DMA timeouts on Promise 20267 IDE card
[please cc: me as I am not subscribed to lkml]
I've recently started getting errors like this (this example is from 2.4.20-pre3-ac2):
Jan 9 14:20:48 carthage kernel: hda: dma_timer_expiry: dma status == 0x61 Jan 9 14:20:48 carthage kernel: hdc: dma_timer_expiry: dma status == 0x21 Jan 9 14:20:58 carthage kernel: hda: timeout waiting for DMA Jan 9 14:20:58 carthage kernel: PDC202XX: Primary channel reset. Jan 9 14:20:58 carthage kernel: PDC202XX: Secondary channel reset. Jan 9 14:20:58 carthage kernel: hda: DMA disabled Jan 9 14:20:58 carthage kernel: hda: timeout waiting for DMA Jan 9 14:20:58 carthage kernel: blk: queue c03c2860, I/O limit 4095Mb (mask 0xffffffff) Jan 9 14:20:58 carthage kernel: hdc: timeout waiting for DMA Jan 9 14:20:58 carthage kernel: PDC202XX: Secondary channel reset. Jan 9 14:20:58 carthage kernel: PDC202XX: Primary channel reset. Jan 9 14:20:58 carthage kernel: hdc: DMA disabled Jan 9 14:20:58 carthage kernel: hdc: timeout waiting for DMA Jan 9 14:20:58 carthage kernel: blk: queue c03c2cac, I/O limit 4095Mb
(mask 0xffffffff)
I have a Promise 20267 PCI IDE controller card on an Epox 8RDA motherboard. The motherboard is brand new and I never got these kinds of errors with my previous MSI K7T Turbo board. There are two drives on the card:
hda: WDC WD400BB-00AUA1, ATA DISK drive
hdc: WDC WD400BB-00DEA0, ATA DISK drive
which are both alone on the seperate controllers. I've tried both 2.4 and 2.5 kernels (2.4.20, 2.4.20-ac2, 2.4.20-pre3-ac2, 2.5.[53-55] and get the same errors.
Does anyone have idea what is causing this? I can offer more information (.config etc) if necessary.
Signature · 2 lines
James Curbo <[email protected]> <[email protected]> http://www.adtrw.org/blogs/hannibal/
Quoted 11 lines · James Curbo
[please cc: me as I am not subscribed to lkml]
I've recently started getting errors like this (this example is from 2.4.20-pre3-ac2):
Jan 9 14:20:48 carthage kernel: hda: dma_timer_expiry: dma status == 0x61 Jan 9 14:20:48 carthage kernel: hdc: dma_timer_expiry: dma status ==
0x21
I believe the low bit set in the dma_status means that the DMA transfer is still in progress. Since the timer has expired, that means it's been in progress for 10 seconds. Odds are the drive has stopped responding. Since it's a Western Digital drive, it probably needs to be powercycled to come back.
I don't think this is a problem with the controller card, but I could be wrong.
Ross
Quoted 11 lines · Ross Biro
I believe the low bit set in the
dma_statusmeans that the DMA transfer is still in progress. Since the timer has expired, that means it's been in progress for 10 seconds. Odds are the drive has stopped responding. Since it's a Western Digital drive, it probably needs to be powercycled to come back.I don't think this is a problem with the controller card, but I could be wrong.
Ross
Well, I have had the first drive for about a year and a half (I think) and the second drive since August. I never had any problems out of them with the same controller card on my previous motherboard (MSI K7T Turbo). The problems didn't arise until the other day when I got my new board.
The errors occur over and over; the drive will come back for a few seconds and then the error will occur again. I usually reboot at this point.
Signature · 2 lines
James Curbo <[email protected]> <[email protected]> http://www.adtrw.org/blogs/hannibal/