> reiserfs: checking transaction log (ide2(33,3)) for (ide2(33,3))
> hde: dma_intr: bad DMA status (dma_stat=36)
> hde: ide_dma_intr: status=0x50 [ drive ready,seek complete]
> hde: request error, nr. 1
How the heck did you get get bit 4 of the dma_status register to report
anything other than "0" ??
Next "HTH", did it manage to invoke an DMA Error and Interrupt and return
a the drive back in to command mode with a 50 stat ?
I have never been so amazed by this driver's ablity to invoke hardware
events that can not happen.
Andre Hedrick
LAD Storage Consulting Group
-
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/