Hide Forgot
I'm getting occaisional disk errors on my machine of the form: hda: status timeout: status=0xd0 { Busy } hda: no DRQ after issuing WRITE ide0: reset: success There has been no evidence (i.e. fsck failures) that these errors have caused actual problems on the disk. The relevant portion of my dmesg follows: PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA hda: ST36421A, ATA DISK drive hdc: SAMSUNG SC-148B, ATAPI CDROM drive ide2: ports already in use, skipping probe ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: ST36421A, 6150MB w/256kB Cache, CHS=784/255/63 hdc: ATAPI 48X CD-ROM drive, 128kB Cache I'm running redhat linux 6.1, and I have a seagate drive. I changed both software and hardware at the same time (I upgraded my computer, which required a new release of linux, so I upgraded my software). My processor is a celeron 400A. I'm happy to provide whatever other information might be required.
A search through dejanews reveals a lively discussion on various mailing lists on this bug. Quick summary: -- It appears to be related to having a seagate drive; possibly it's simple using a UDA66 drive on a UDA33 controller. -- Reactions have ranged from "your drives about to die" to "linux deals with those; don't worry about it". -- Fixes suggested have ranged from "Recheck your cables" to "load the new driver" to "adjust your BIOS specs by hand". Unfortunately, the most authoritative answer seems to be to adjust BIOS specs, and details weren't given on how to do this.
Assigned to dledford
I resolved this problem by disabling UDMA in the system BIOS in three different systems - Each with different BIOS's - That is why there are no details on how to do this in the news groups.
If that didnt work for you re-open this one.