> On Fri, Apr 02, 1999 at 11:18:23PM -0600, Andre M. Hedrick wrote:
>
I've started seeomg the same problems on hda and hdb
> > Care to name the chipset and drive combination with revisions?
>
> Intel VX440 mainboard;
>
Intel 440BX mainboard.
> PIIX3: IDE controller on PCI bus 00 dev 39
> PIIX3: not 100ative mode: will probe irqs later
> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
>
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:pio, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: QUANTUM BIGFOOT_CY4320A, ATA DISK drive
hdb: QUANTUM FIREBALL_TM1700A, ATA DISK drive
hdc: PHILIPS CDD3610 CD-R/RW, ATAPI CDROM drive
hdh: probing with STATUS(0x00) instead of ALTSTATUS(0x80)
hdh: WEARNES CDD-1020, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide3 at 0x168-0x16f,0x36e on irq 10
hda: QUANTUM BIGFOOT_CY4320A, 4134MB w/67kB Cache, CHS=527/255/63, DMA
hdb: QUANTUM FIREBALL_TM1700A, 1628MB w/76kB Cache, CHS=827/64/63, DMA
(ide3 is on an sb)
> > Usually the chipset and the drive are not communicating at the same
> > rates or one the two devices (drive or host adapter/mainboard)
> > failed to correctly recognize one or the other. Manufacturer
> > forgot to read something.
>
> It works 99% of the time, just every now and then, perhaps once a day under
> light load, more often under heavier load, I get these:
>
> hda: timeout waiting for DMA
> hda: irq timeout: status=0xd0 { Busy }
> ide0: reset: success
>
Same here. Sometimes it then disables DMA on the drive as well.
HTH
-- Mike <rickettm@ox.compsoc.net>Oh what a tangled web we weave, when first we practice to deceive. -- Shakespeare
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/