hda: timeout waiting for DMA
Este problema me viene de lejos, y tambien me viene grande por lo visto.
Pues eso, que no soy capaz de atajarlo, y me realentiza enormemente el
sistema. Me han dicho que puede ser de una mala configuracion del kernel.
Si alguien me puede hechar una mano se lo agradeceria.
Nov 1 22:30:55 localhost kernel: hda: timeout waiting for DMA
Nov 1 22:30:55 localhost kernel: hda: irq timeout: status=0xd2 { Busy }
Nov 1 22:30:55 localhost kernel: hda: DMA disabled
Nov 1 22:30:55 localhost kernel: ide0: reset: success
Nov 1 22:30:55 localhost kernel: hda: irq timeout: status=0xd0 { Busy }
Nov 1 22:30:55 localhost kernel: ide0: reset: success
Nov 1 22:30:55 localhost kernel: hda: irq timeout: status=0xd0 { Busy }
Nov 1 22:30:55 localhost kernel: ide0: reset: success
Gracias.
Re: hda: timeout waiting for DMA
[EMAIL PROTECTED]([EMAIL PROTECTED])@01.11.2001 22:44:22 +:
Nov 1 22:30:55 localhost kernel: hda: timeout waiting for DMA
Nov 1 22:30:55 localhost kernel: hda: irq timeout: status=0xd2 { Busy }
Nov 1 22:30:55 localhost kernel: hda: DMA disabled
Nov 1 22:30:55 localhost kernel: ide0: reset: success
Nov 1 22:30:55 localhost kernel: hda: irq timeout: status=0xd0 { Busy }
Nov 1 22:30:55 localhost kernel: ide0: reset: success
Nov 1 22:30:55 localhost kernel: hda: irq timeout: status=0xd0 { Busy }
Nov 1 22:30:55 localhost kernel: ide0: reset: success
Hola.
A mi me pasaba lo mismo y lo solucioné activando el DMA para el disco:
# hdparm -d1 /dev/hda
Echa un vistazo a la página de manual de hdparm(8) para ver todas las
opciones disponibles. Debes tener precaución al usar este comando,
puedes perder toda la información del disco.
Para estimar el rendimiento del disco prueba a ejecutar:
# hdparm -tT /dev/hda
Opciones interesantes, además del DMA son -m (multiple sctors), -c
(32-bit). Con -i obtienes la información sobre tu disco duro.
Saludos
--
Jesús Ángel del Pozo Domínguez
Valladolid __ô
GnuPG key-id: 0x17FB6CCE _ \_
http://www.tel.uva.es/~jpozdom (_)/(_)
_
|.---.|
A Prayer to my|| _ ||
COMPUTER ANGEL: || (\o/) ||
||/_\||
Guide my keystrokes,||___||
Keep my programs alive, `-)---(-'
Protect me from Windows, [=== -- o ]--.
Back up my drive. __'-'__ \
[::: :::] )
Exit. `''`/T\
jgs \_/
hde timeout waiting for DMA ... HELP!!
Hi everyone, I think there is numerous posting on this subject, but I don't really know what is going on. Anyway, I have a Promise ATA100 on P3V4X. When I tried to install 2.2 from scratch and doing a dpkg installation. hde timeout waiting for DMA errow showed up. I am using Maxtor 91024U4 hd ATA66. It doesn't seem to produce any weird sound. Anyone has any suggestion for what I should do? buy a know hd? Also can CR-4028TE use 80 pin cable with no problem? thanx everyone... I need your help.. Edwin Lau
timeout waiting for DMA
Hey people.
I'm trying to enable DMA on my wife's harddrive. Here's some info.
poohbear:/proc# hdparm -i /dev/hda
/dev/hda:
Model=FUJITSU MPF3102AT, FwRev=0031, SerialNo=05601857
Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=0(?), BuffSize=512kB, MaxMultSect=16, MultSect=16
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=20015856
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
IORDY=yes, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 mode2 mode3 *mode4
Now, when I try to enable DMA...
poohbear:/proc# hdparm -d1 -X34 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
setting xfermode to 34 (multiword DMA mode2)
using_dma= 1 (on)
I get this in the syslog:
May 5 07:17:16 poohbear kernel: hda: timeout waiting for DMA
May 5 07:17:16 poohbear kernel: hda: irq timeout: status=0x58 { DriveReady
SeekComplete DataRequest }
May 5 07:17:16 poohbear kernel: hda: status timeout: status=0xd0 { Busy }
May 5 07:17:16 poohbear kernel: hda: DMA disabled
May 5 07:17:16 poohbear kernel: hda: drive not ready for command
May 5 07:17:17 poohbear kernel: ide0: reset: success
Any ideas on this? Could this also be related to why I can't get her sound
to work?
Thanks, I'd love to get this working for her.
Mike
--
Michael P. Soulier [EMAIL PROTECTED]
With sufficient thrust, pigs fly just fine. However, this is not necessarily a
good idea. It is hard to be sure where they are going to land, and it could be
dangerous sitting under them as they fly overhead. -- RFC 1925
pgpOEurqMHnHE.pgp
Description: PGP signature
Re: timeout waiting for DMA
On Sat, May 05, 2001 at 07:26:09AM -0400, Michael P. Soulier wrote: Hey people. I'm trying to enable DMA on my wife's harddrive. Here's some info. I'm not sure if this is of any help to you, but I did the same here, and I used this article as a guide: http://www.oreillynet.com/pub/a/linux/2000/06/29/hdparm.html Maybe you're missing a parameter somewhere. -- Alex Suzuki | [EMAIL PROTECTED] | http://www.cynox.ch To send me an email, remove NOSPAM from the above address
Re: timeout waiting for DMA
On Sat, May 05, 2001 at 02:21:46PM +0200, Alex Suzuki wrote: I'm not sure if this is of any help to you, but I did the same here, and I used this article as a guide: http://www.oreillynet.com/pub/a/linux/2000/06/29/hdparm.html Maybe you're missing a parameter somewhere. Yeah, I used it too. It just doesn't seem to like DMA. Would that prevent a soundcard from working, or is that a different kind of DMA? Mike -- Michael P. Soulier [EMAIL PROTECTED] With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925 pgp8oB9a6R1cj.pgp Description: PGP signature
Re: hda timeout waiting for DMA?
On 23 Apr 2001, at 19:19, Stephen E. Hargrove wrote:
I've got a server that's been running for quite some time now with no
problems. Actually, it's running right now. However, just today, I've
noticed some log entries I've never seen before:
Apr 23 15:22:27 cx633007-b kernel: hda: timeout waiting for DMA
Apr 23 15:22:27 cx633007-b kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
Apr 23 15:22:27 cx633007-b kernel: hda: irq timeout: status=0x58 {
DriveReady SeekComplete DataRequest }
hrm . . . anyone have any idea as to what might be going on?
I had a similar message come up with hdc:
hdc: timeout waiting for DMA
hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
Finally worked out that the system had been working fine (no timeouts) prior to
me compiling up a firewall enabled kernel. I initally installed Debian
2.2.18pre21-compact. Comparing the config- files I found that I had set the
option CONFIG_IDEDMA_AUTO to Y in my new kernel. make menuconfig lists this
option under: Block Devices - Use DMA by default when availble. Removing this
option (ie setting it to N) has fixed my system - havent had the timeout
message
since.
HTH
Lex
---==--==--==--==---
Lex McPhail
Systems Analyst/Programmer
Systems Software Instrumentation Ltd
Christchurch
New Zealand
email: [EMAIL PROTECTED]
Re: hda timeout waiting for DMA?
On Tue, 24 Apr 2001, Lex McPhail wrote:
I had a similar message come up with hdc:
hdc: timeout waiting for DMA
hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
Finally worked out that the system had been working fine (no timeouts) prior
to
me compiling up a firewall enabled kernel. I initally installed Debian
2.2.18pre21-compact. Comparing the config- files I found that I had set the
option CONFIG_IDEDMA_AUTO to Y in my new kernel. make menuconfig lists this
option under: Block Devices - Use DMA by default when availble. Removing
this
option (ie setting it to N) has fixed my system - havent had the timeout
message
since.
i find this very odd, considering that i haven't made any modifications to
this particular system in several months. however
hdparm -d 0 /dev/hda
and the message has stopped appearing. this particular drive shouldn't
have been configured to use dma anyway, so disabling dma makes perfect
sense.
--
steve
*
linux : http://exitwound.org
mozart: http://mozart.sourceforge.net
buck : http://www.BuckOwensFan.com
*
Re: hda timeout waiting for DMA?
On Tue, Apr 24, 2001 at 09:01:04AM -0500, Stephen E. Hargrove wrote: i find this very odd, considering that i haven't made any modifications to this particular system in several months. however hdparm -d 0 /dev/hda and the message has stopped appearing. this particular drive shouldn't have been configured to use dma anyway, so disabling dma makes perfect sense. Is it a western digital? Really old? Do you have an unsupported chipset? Maybe we can get you using some form of dma with this drive. Post the output of lspci. Post the output of hdparm -i /dev/hda Mike
Re: hda timeout waiting for DMA?
On Tue, 24 Apr 2001, Mike Fedyk wrote:
Is it a western digital? Really old? Do you have an unsupported chipset?
Yes, it's a WD. Probably 5 years old, max. The chipset (which escapes me
at the moment) is support, to the best of my recollection.
Maybe we can get you using some form of dma with this drive.
Post the output of hdparm -i /dev/hda
/dev/hda:
Model=WDC AC38400B, FwRev=32.02S32, SerialNo=WD-WM6210073506
Config={ HardSect NotMFM HdSw15uSec SpinMotCtl Fixed DTR5Mbs FmtGapReq
}
RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=22
BuffType=DualPortCache, BuffSize=512kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=16514064
IORDY=on/off, tPIO={min:160,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 *mdma2 udma0 udma1 udma2
Post the output of lspci.
see the text attachment.
--
steve
*
linux : http://exitwound.org
mozart: http://mozart.sourceforge.net
buck : http://www.BuckOwensFan.com
*
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort+ SERR- PERR-
Latency: 24 set
00:07.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] (rev
01)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR-
Latency: 0 set
00:07.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
(prog-if 80)
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR-
Latency: 16 set
Region 4: I/O ports at ff50
00:0b.0 Network controller: Unknown device 14b7:0001 (rev 02)
Subsystem: Unknown device 14b7:0001
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ffbbfc00 (32-bit, non-prefetchable)
Region 1: I/O ports at fc80
Region 3: I/O ports at ff60
00:0f.0 VGA compatible controller: S3 Inc. ViRGE/VX (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR-
Latency: 4 min, 255 max, 24 set
Interrupt: pin A routed to IRQ 11
Region 0: Memory at f800 (32-bit, non-prefetchable)
00:11.0 Multimedia audio controller: Creative Labs SB Live! (rev 07)
Subsystem: Unknown device 1102:8061
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR-
Latency: 2 min, 20 max, 24 set
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at ff80
Capabilities: [dc] Power Management version 1
Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME-
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:11.1 Input device controller: Creative Labs SB Live! Daughterboard (rev 07)
Subsystem: Unknown device 1102:0020
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR-
Latency: 24 set
Region 0: I/O ports at fff0
Capabilities: [dc] Power Management version 1
Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME-
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:13.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown
device 4d30 (rev 02)
Subsystem: Unknown device 105a:4d33
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR-
Latency: 24 set
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at ffe0
Region 1: I/O ports at ffac
Region 2: I/O ports at ffa0
Region 3: I/O ports at ffa8
Region 4: I/O ports at ff00
Region 5: Memory at ffbc (32-bit, non-prefetchable)
Capabilities: [58] Power Management version 1
Flags: PMEClk- AuxPwr- DSI- D1- D2- PME-
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Re: hda timeout waiting for DMA?
On Tue, Apr 24, 2001 at 03:06:38PM -0500, Stephen E. Hargrove wrote:
On Tue, 24 Apr 2001, Mike Fedyk wrote:
Is it a western digital? Really old? Do you have an unsupported chipset?
Yes, it's a WD. Probably 5 years old, max. The chipset (which escapes me
at the moment) is support, to the best of my recollection.
Maybe we can get you using some form of dma with this drive.
Post the output of hdparm -i /dev/hda
/dev/hda:
Model=WDC AC38400B, FwRev=32.02S32, SerialNo=WD-WM6210073506
Config={ HardSect NotMFM HdSw15uSec SpinMotCtl Fixed DTR5Mbs FmtGapReq
}
RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=22
BuffType=DualPortCache, BuffSize=512kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=16514064
IORDY=on/off, tPIO={min:160,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 *mdma2 udma0 udma1 udma2
From all of the messages I've seen on lkml, I wouldn't enable dma unless
you're feeling adventurous. You can use hdparm -m16 -c3, and it should give
you a performance boost.
I have a 35GB WD that I'm going to play with to see if I can get it working
with dma reliably.
If you do, I'd compile a kernel with the ide patch to get more features of
your ide chipset (PIIX3) supported.
hda timeout waiting for DMA?
I've got a server that's been running for quite some time now with no
problems. Actually, it's running right now. However, just today, I've
noticed some log entries I've never seen before:
Apr 23 15:22:27 cx633007-b kernel: hda: timeout waiting for DMA
Apr 23 15:22:27 cx633007-b kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
Apr 23 15:22:27 cx633007-b kernel: hda: irq timeout: status=0x58 {
DriveReady SeekComplete DataRequest }
hrm . . . anyone have any idea as to what might be going on?
--
steve
*
linux : http://exitwound.org
mozart: http://mozart.sourceforge.net
buck : http://www.BuckOwensFan.com
*
Re: hda timeout waiting for DMA?
On Mon, Apr 23, 2001 at 07:19:17PM -0500, Stephen E. Hargrove wrote:
I've got a server that's been running for quite some time now with no
problems. Actually, it's running right now. However, just today, I've
noticed some log entries I've never seen before:
Apr 23 15:22:27 cx633007-b kernel: hda: timeout waiting for DMA
Apr 23 15:22:27 cx633007-b kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
Apr 23 15:22:27 cx633007-b kernel: hda: irq timeout: status=0x58 {
DriveReady SeekComplete DataRequest }
hrm . . . anyone have any idea as to what might be going on?
Is your hard drive making any unusual sounds? This is usually a sign
that the HD is going bad or is bad. I would make a backup quick if you
don't have one. I've seen reported on this mail list people successfully
using hdparm to straiten things out but ymmv. You can search the list
archives for timeout status SeekComplete etc. and come up with
lots of hits.
hth,
kent
--
From seeing and seeing the seeing has become so exhausted
First line of The Panther - R. M. Rilke
Re: hda timeout waiting for DMA?
On Mon, Apr 23, 2001 at 08:57:54PM -0500, ktb wrote:
On Mon, Apr 23, 2001 at 07:19:17PM -0500, Stephen E. Hargrove wrote:
I've got a server that's been running for quite some time now with no
problems. Actually, it's running right now. However, just today, I've
noticed some log entries I've never seen before:
Apr 23 15:22:27 cx633007-b kernel: hda: timeout waiting for DMA
Apr 23 15:22:27 cx633007-b kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
Apr 23 15:22:27 cx633007-b kernel: hda: irq timeout: status=0x58 {
DriveReady SeekComplete DataRequest }
hrm . . . anyone have any idea as to what might be going on?
Is your hard drive making any unusual sounds? This is usually a sign
that the HD is going bad or is bad. I would make a backup quick if you
don't have one. I've seen reported on this mail list people successfully
using hdparm to straiten things out but ymmv. You can search the list
archives for timeout status SeekComplete etc. and come up with
lots of hits.
hth,
kent
Don't say that to quick. I get that exact error when I have hdparm set my
hd to a mode it doesn't like.
What has change recently? New kernel? You using the ide patch for 2.2?
run this:
find /etc -type f | xargs grep -il hdparm
It'll list files that have hdparm in them.
Look at the file and see if it's being run on startup, or when you see this
error...
Mike
Re: hdc: timeout waiting for DMA
On Mon, Mar 26, 2001 at 02:09:13PM +1200, Lex McPhail wrote:
| What does the following message mean:
|
| hdc: timeout waiting for DMA
| hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
|
The drive is probably going bad, or you might just have a bad machine.
About a month and a half ago I got errors like this (then the ide bus
would reset it would try again, and again ..., and I couldn't do
anything but pull the plug). I saved all my data, ran Maxtor's
diagnostic utilities (I have a Maxtor drive) and it said all was fine.
I reinstalled Debian, and last night got the errors again. This time
I unplugged my zip drive, and the machine was ok. My box only has a
110 watt power supply, so I think I was pushing it over its limit and
the hd really is fine. If you have a similar situation with your box,
try removing disks you don't really use and see if the problem goes
away. If it does, live without the disks or get a bigger power
supply.
HTH,
-D
hdc: timeout waiting for DMA
What does the following message mean:
hdc: timeout waiting for DMA
hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
It is coming up on my Debian 2.2.18pre21 potato installation quite regularly
since I have compiled up a kernel to make the system a firewall + ipmasq
computer.
I cant remember it coming up when I was running the kernel I initially
downloaded: Debian 2.2.18pre21-compact.
hdc is a QUANTIUM FIREBALL ST2.1A
Anyone got any ideas where I should go from here?
Re: hdc: timeout waiting for DMA
On Mon, Mar 26, 2001 at 02:09:13PM +1200, Lex McPhail wrote:
What does the following message mean:
hdc: timeout waiting for DMA
hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
It is coming up on my Debian 2.2.18pre21 potato installation quite regularly
since I have compiled up a kernel to make the system a firewall + ipmasq
computer.
I cant remember it coming up when I was running the kernel I initially
downloaded: Debian 2.2.18pre21-compact.
hdc is a QUANTIUM FIREBALL ST2.1A
Anyone got any ideas where I should go from here?
Usually this is a sign the drive is going bad. I would recommend
pulling off any info you want to save and then try your old kernel and
see if the errors still exist. Take a look in the archives I have seen
people tweak with hdparm and straiten things out but ymmv.
kent
--
From seeing and seeing the seeing has become so exhausted
First line of The Panther - R. M. Rilke
Re: hdc: timeout waiting for DMA
On Mon 26 Mar 01, 2:09 PM, Lex McPhail said:
What does the following message mean:
hdc: timeout waiting for DMA
hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
i think it means linux wanted to do an operation, sent the request, waited
for the IRQ to say i'm done but never got the interrupt.
Anyone got any ideas where I should go from here?
unfortunately not. best advice i can give is make sure the IDE ribbon cable
is tightly in place and the the power cable is in too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
--
Coffee... I've conquered the Borg on coffee! [EMAIL PROTECTED]
-- Kathryn Janeway on the virtues of coffee www.dirac.org/p
Re: hdc: timeout waiting for DMA
Thus spake Lex McPhail ([EMAIL PROTECTED]):
hdc: timeout waiting for DMA
hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hdc is a QUANTIUM FIREBALL ST2.1A
It could be one of two things.
It could be caused by a buggy IDE controller (PIIX3 is one such example) that
advertises itself as a BM-DMA controller without fully supporting the
standard.
Try turning off DMA on all devices on that controller by using hdparm -d0
[device].
Another possibility is the hard disk is beginning to fail. Are you getting
any other errors? Do you hear any clicking, grinding, or harmonic noises
coming from the disk? If so, throw the data to tape or a good hard disk and
replace it. Even though I have had no problems with Quantum Fireball drives,
IDE drives in general are not exactly built in a quality fashion, if you hear
any odd noises or begin to get I/O errors, or bus resets, replace it
immediately.
--
oneiros [EMAIL PROTECTED]1024D/62C2F77D
url: http://oneiros.darkspire.net/ EBB8 AF14 8C43 2F12 7623
irc: EFnet / opn C0AA C0AE 56D4 62C2 F77D
Re: hdc: timeout waiting for DMA -- extended
hi all,
On Mon 26 Mar 01, 2:09 PM, Lex McPhail said:
What does the following message mean:
hdc: timeout waiting for DMA
hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
i think it means linux wanted to do an operation, sent the request, waited
for the IRQ to say i'm done but never got the interrupt.
i got a whole bunch of these this morning and then our debian 2.2.17 system
crashed with the following:
kernel panic LFS: VRU block list corrupted
i cant seem to find out what that means anywhere? i rebooted and changed the
drive in question, but can anyone explain what this is about?
Regards,
Marc-Adrian Napoli
Network Administrator
Connect infobahn Australia
+61 2 92120387
