Messages in this thread | | | Date | Fri, 28 Sep 2001 14:54:48 +0200 | From | Vojtech Pavlik <> | Subject | Re: ide drive problem? |
| |
On Fri, Sep 28, 2001 at 01:52:22PM +0200, clemens wrote: > Hi David, Hi Steve > > i get: > > hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hde: dma_intr: error=0x84 { DriveStatusError BadCRC } > > on: > > Linux version 2.4.9-ac7 (root@ghanima) (gcc version 2.95.4 20010902 (Debian > prerelease)) #1 SMP Wed Sep 26 14:39:37 CEST 2001 > > HPT370: IDE controller on PCI bus 00 dev 98 > PCI: Found IRQ 15 for device 00:13.0 > HPT370: chipset revision 3 > HPT370: not 100% native mode: will probe irqs later > ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:DMA, hdf:pio > ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:pio, hdh:pio > hde: ST360021A, ATA DISK drive > > even thou i have VT8363/8365 (=KT133) as north bridge, and VT82C686A as > southbridge, at least the south bridge could not be blamed for that, since > a. i don't even use it, hde is my hpt370 controller, and > b. it's the A revision and not the infamous 686B revision (see > http://www.viahardware.com/686bfaq.shtm for more infos on "the" 686B bug) > > what kernel, harddisc do you both have? > > clemens > > p.s.: i don't know if "BadCRC" has anything to do with bad blocks, but > /sbin/badblocks doesn't even show a single bad block on my brand new seagate > disc, so i guess, that's not the source of the troubles.
It means that the drive detected a bad CRC on the UDMA transaction. Unless these are frequent, they are harmless, since the transaction will be retried..
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |