Computing.Net > Forums > Linux > Anybody, I REALLY need advice!!

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Anybody, I REALLY need advice!!

Reply to Message Icon

Name: Damien
Date: December 19, 2001 at 23:29:58 Pacific
Comment:

Hi,

I have posted here before about a harddrive
problem in mandrake 8.1. I have a western
digital 7200 rpm 40gb hdd, amd 1.4GHz CPU,
512Mb ddr ram, MSI k7T266 Pro Motherboard
(no raid), panasonic DVD rom, Acer 40x16x10
burner...

The problem has been that linux will appear
to shutdown my hdd, randomly.. There
doesn't appear to be a pattern to it, not
length of time linux has been up, disk
activity, application.. nothing... it has
happened on bootup, surfing the web,
loading konqueror, and recompiling a new
kernel. The messages I Get are:

15493 Dec 20 17:36:08 thebeast kernel:
hda: timeout waiting for DMA
15494 Dec 20 17:36:08 thebeast kernel:
ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
15495 Dec 20 17:36:08 thebeast kernel:
hda: read_intr: status=0x51 { DriveReady
SeekComplete Error }
15496 Dec 20 17:36:08 thebeast kernel:
hda: read_intr: error=0x04 {
DriveStatusError }
15497 Dec 20 17:36:08 thebeast kernel:
hda: read_intr: status=0x51 { DriveReady
SeekComplete Error }
15498 Dec 20 17:36:08 thebeast kernel:
hda: read_intr: error=0x04 {
DriveStatusError }
15499 Dec 20 17:36:08 thebeast kernel:
hda: read_intr: status=0x51 { DriveReady
SeekComplete Error }
15500 Dec 20 17:36:08 thebeast kernel:
hda: read_intr: error=0x04 {
DriveStatusError }
15501 Dec 20 17:36:08 thebeast kernel:
hda: read_intr: status=0x51 { DriveReady
SeekComplete Error }
15502 Dec 20 17:36:08 thebeast kernel:
hda: read_intr: error=0x04 {
DriveStatusError }
15503 Dec 20 17:36:08 thebeast kernel:
ide0: reset: success
15504 Dec 20 17:36:28 thebeast kernel:
hda: timeout waiting for DMA
15505 Dec 20 17:36:28 thebeast kernel:
ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
15506 Dec 20 17:37:09 thebeast kernel:
hda: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
15507 Dec 20 17:37:09 thebeast kernel:
hda: drive not ready for command
15508 Dec 20 17:37:09 thebeast kernel:
hda: timeout waiting for DMA
15509 Dec 20 17:37:09 thebeast kernel:
ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
15510 Dec 20 17:37:09 thebeast kernel:
hda: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
15511 Dec 20 17:37:09 thebeast kernel:
hda: drive not ready for command
15512 Dec 20 17:37:09 thebeast kernel:
hda: timeout waiting for DMA
15513 Dec 20 17:37:09 thebeast kernel:
ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
15514 Dec 20 17:37:09 thebeast kernel:
hda: status error: status=0x58 { DriveReady
SeekComplete DataRequest }


that is the complete transcript of what
happened last time... I had upgraded to
kernel 2.4.14 after the first few times to
see if that would fix it... but it has
happened twice with the new one as well..

Please I'm desperate to get some advice, if
you don't know what the problem is, can u
point me to somewhere where I can get
help?? Everything else in my linux system
is set up perfectly and working like a
charm, but this one problem is really
annoying and I don't like it doing strange
things to my hdd (the problem has never
happened in windows).
Thank you to anybody that replies!

Damien



Sponsored Link
Ads by Google

Response Number 1
Name: Anthony Foot
Date: December 20, 2001 at 04:56:11 Pacific
Reply:

To me this does not look like a problem with Linux. It looks more like a hardware problem with either your hard disk or IDE controller.

Thanks,

Anthony.


0

Response Number 2
Name: Damien
Date: December 20, 2001 at 05:46:00 Pacific
Reply:

This problem only occurs under linux. All of the components are brand new. I dual boot between linux and windows 98/2000... the windows OS's don't have problems with the hdd. Under linux i get the sound of the hard drive turning off, then it starts grinding away for a while, then after about a minute it is back on... it happens only very occasionally, but enough to annoy the hell out of me..
I am so very close to having a perfect linux install, just need the usbmouse driver to stop stuffing up, and this hard drive problem to go away...

Damien


0

Response Number 3
Name: Josh
Date: December 20, 2001 at 14:51:50 Pacific
Reply:

It could be a bios issue.
You can see siminal problems with Windows running on Laptops, where your power management will shutdown your hard drive or video after a set amount of idle time... I haven't had this happen on my Mandrake 8.1 system running on a Conmpaq P2-350, but then again in my bios settings I have disabled advanced power management.


0

Response Number 4
Name: Guy Allard
Date: December 20, 2001 at 17:52:25 Pacific
Reply:

Things you could try (all somewhat dangerous):

1) Experiment with any 'Power Mangement' options in your BIOS.

2) Turn off/on the 'PNP OS' option in your BIOS.

3) Build and boot a custom kernel with all power mangement functions excluded from the build.

I tend to agree that if the WinX systems do not have a problem, then it is probably not a hardware problem (-probably-).

Luck, Guy


0

Response Number 5
Name: Greg
Date: December 20, 2001 at 21:19:43 Pacific
Reply:

It seems to me that there may be an incompatibility with the DMA function on the hard drive. Try disabling DMA, which may help, but may give you less performance on your hard drive. To do so, you can use the hdparm command.

to see the current status of DMA:
hdparm -d /dev/hda

To disable DMA: hdparm -d 0 /dev/hda

To enable DMA: hdparm -d 1 /dev/hda

To perform a HD speed test:
hdparm -t -T /dev/hda

Good Luck.

Greg


0

Related Posts

See More



Response Number 6
Name: Anthony Foot
Date: December 21, 2001 at 00:49:38 Pacific
Reply:

This link may help:
http://www.mandrakeuser.org/docs/hardware/hide2.html


0

Response Number 7
Name: Damien
Date: December 22, 2001 at 19:11:53 Pacific
Reply:

Hey, thanks for all the replies!

It doesn't appear to be an APM problem because it happened while APM was disabled in the bios and when the apm daemon wasn't loaded. I now have APM on in the bios (linux now turns off my computer, yay! :) ), I haven't had it happen with apm on yet, but it's only happens occasionally anyway so time will tell...

I think it may be a bug in the via kt266 chipset, there are a number of bugs in this chipset :/ One of the bugs is some sort of overflow problem, im still trying to find it on the net. VIA have recently started supporting linux (well, sort of), hopefully this support will grow over time and we'll get some drivers from them to fix the problem. The reason it doesn't happen in windows is the via 4-in-1 drivers disable the 'feature' that causes the overflow.
I'm just going to keep ugrading my kernel until the hdd problem is fixed and the usb mouse problem is fixed, until then I just have to put up with it.

btw, how can i tell if my hard drive is working at ATA-100 ? i did the hdparm speed test, but i don't know if they are typical values for a 7200rpm drive on an ata-100 compatible chipset. Here are the values:

Timing buffer-cache reads: 128 MB in 0.62 seconds =206.45 MB/sec
Timing buffered disk reads: 64 MB in 2.08 seconds = 30.77 MB/sec
the last value seems kinda crappy..

thanks for the support guys!

Damien



0

Response Number 8
Name: wvdave
Date: January 14, 2002 at 02:33:53 Pacific
Reply:

i see you have a dvd and a burner going. are they two ide's running on one channel


0

Response Number 9
Name: Debian User
Date: January 29, 2002 at 02:15:09 Pacific
Reply:

I just had this problem, too - and solved it by upgrading to 2.4.17
and enabling the Promise IDE chip (it's part of the black devices section).

http://www.van-dijk.net/linuxkernel/200151/0782.html

may help. Just crawl through make xconfig ensuring that
if you've got hardware, the kernel knows about it.

HTH!


0

Response Number 10
Name: Larry Tobos
Date: March 7, 2002 at 19:06:24 Pacific
Reply:

I get the "ide_dmaproc: chipset supported ide_dma_timeout func only:14" message and a hard lock of my system with a Samsung CD-RW and the 2.4.* kernels. Disabling DMA with "hdparm -d0 /dev/hdc" solves it (hdc is my CDRW). I don't have this problem with 2.2. kernels though !!


0

Response Number 11
Name: RAUL NARANJO R.
Date: March 15, 2002 at 10:15:08 Pacific
Reply:

I have the same problem using Storm Linux after i upgraded from Debian.

I simply remove APM package and everyting works fine now!

Try it, you have nothing to lose.

:)


0

Response Number 12
Name: paul robson
Date: March 22, 2002 at 19:03:19 Pacific
Reply:

I have the same problem on an old Patriot machine.

What happens is the DMA doesn't, basically, work, so you need to disable it, usually using HDPARM or kernel recomp. Sticking hdparm calls in rc.local works fine. This seems to be present in all 2.4 kernels and no 2.2 kernels as far as I can tell.

Warning, 2.4.19 will not boot from CDROM (the Peanut 9.2 distro) as on my machine it kicks in the 66Mhz UDMA and Linux can't load the HDD partition table. So I'd be wary of upgrading too much. 2.4.17 works fine... providing DMA is disabled.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Linux Forum Home


Sponsored links

Ads by Google


Results for: Anybody, I REALLY need advice!!

Can I run Microsoft Word with Linux www.computing.net/answers/linux/can-i-run-microsoft-word-with-linux/24010.html

No More MS, need advice on Linux! www.computing.net/answers/linux/no-more-ms-need-advice-on-linux/24039.html

I need to know this fast. www.computing.net/answers/linux/i-need-to-know-this-fast/25517.html