>hda: dma_timer_expiry: dma status == 0x21
>hda: timeout waiting for DMA
>ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>hda: dma_timer_expiry: dma status == 0x21
>hdc: dma_timer_expiry: dma status == 0x61
>hda: timeout waiting for DMA
>ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>hda: dma_timer_expiry: dma status == 0x21
>hdc: dma_timer_expiry: dma status == 0x61
>hda: timeout waiting for DMA
>ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>hda: dma_timer_expiry: dma status == 0x21
>hdc: dma_timer_expiry: dma status == 0x61
>hda: timeout waiting for DMA
>ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>I also noticed this only happened when bonnie'ing on the hda disk (An ugly
>big noisy Quantum Bigfoot) - the hdc seems to work flawlessly. So this might
>as well be a hardware related problem that previusly didn't lock up the
>kernel.
FWIW, this happens on a stock 2.2.14 kernel with a big not very noisy
Quantum Bigfoot CY on /dev/hda:
kernel: PIIX4: IDE controller on PCI bus 00 dev 21
kernel: PIIX4: not 100ative mode: will probe irqs later
kernel: ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
kernel: ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA
kernel: hda: QUANTUM BIGFOOT_CY6480A, ATA DISK drive
kernel: hdc: IBM-DJNA-372200, ATA DISK drive
kernel: hdd: QUANTUM FIREBALL ST6.4A, ATA DISK drive
kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
kernel: ide1 at 0x170-0x177,0x376 on irq 15
kernel: hda: QUANTUM BIGFOOT_CY6480A, 6204MB w/67kB Cache, CHS=790/255/63, DMA
kernel: hdc: IBM-DJNA-372200, 21557MB w/1966kB Cache, CHS=43800/16/63, UDMA
kernel: hdd: QUANTUM FIREBALL ST6.4A, 6149MB w/81kB Cache, CHS=13328/15/63, UDMA
and whenever we write more than a meg or two of data to hda:
kernel: hda: timeout waiting for DMA
kernel: hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
kernel: hda: DMA disabled
kernel: ide0: reset: success
There never seems to be problems reading from the drive, just writing to
it.
The problem may not directly be DMA related. A while ago, the same disk
was on /dev/hdc running in PIO mode (since some sort of bug in 2.2.9-14
means it won't automatically enable non-Ultra DMA except on hda) with
kernel 2.2.9:
kernel: PIIX4: IDE controller on PCI bus 00 dev 21
kernel: PIIX4: not 100ative mode: will probe irqs later
kernel: ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
kernel: ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
kernel: hda: QUANTUM FIREBALL ST6.4A, ATA DISK drive
kernel: hdc: QUANTUM BIGFOOT_CY6480A, ATA DISK drive
kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
kernel: ide1 at 0x170-0x177,0x376 on irq 15
kernel: hda: QUANTUM FIREBALL ST6.4A, 6149MB w/81kB Cache, CHS=784/255/63, UDMA
kernel: hdc: QUANTUM BIGFOOT_CY6480A, 6204MB w/67kB Cache, CHS=790/255/63
and when writing data to it:
kernel: hdc: write_intr: status=0x11 { SeekComplete Error }
kernel: hdc: write_intr: error=0x04 { DriveStatusError }
kernel: hdc: status error: status=0x11 { SeekComplete Error }
kernel: hdc: status error: error=0x04 { DriveStatusError }
kernel: hdc: drive not ready for command
kernel: hdc: status error: status=0x11 { SeekComplete Error }
kernel: hdc: status error: error=0x04 { DriveStatusError }
kernel: hdc: drive not ready for command
kernel: hdc: status error: status=0x11 { SeekComplete Error }
kernel: hdc: status error: error=0x04 { DriveStatusError }
kernel: hdc: drive not ready for command
kernel: ide1: reset: success
Regards,
/ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻTŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ\
| Rask Ingemann Lambertsen | E-mail: mailto:rask@kampsax.k-net.dk |
| Please do NOT Cc: to me or the | WWW: http://www.gbar.dtu.dk/~c948374/ |
| mailing list. I am on the list.| "ThrustMe" on XPilot, ARCnet and IRC |
| If a train station is where a train stops, what is a workstation then? |
-
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/