[CLUE-Tech] kernel drivers
Mike Staver
staver at fimble.com
Tue Aug 24 15:45:00 MDT 2004
I'm getting this kind of message on a Suse 9.1 box when running dmesg:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I've seen the exact same thing under RH 7.x - 9.x, and Suse 9.0. I
figured I had a bad drive... so I bought a new one. Then I reinstalled,
and it's still happening. So I swapped cables, and it's still
happening. Here are the specs:
timmy:/home/staver # /sbin/hdparm -i /dev/hda
/dev/hda:
Model=Maxtor 6Y080L0, FwRev=YAR41BW0, SerialNo=Y2TMF0WE
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=160086528
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5 udma6
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):
* signifies the current active mode
Has anybody seen this before, and if so, could you fix it? I'm guessing
it's either an old bios, defective ide controller, or the kernel needs
tweaking.
--
-Mike Staver
staver at fimble.com
mstaver at globaltaxnetwork.com
More information about the clue-tech
mailing list