It tells you the chipset doesnt support an IDE dma timeout handling function
(ie all it can do is reset and retry)
> 2. it's usually a sign of "mkfs + reinstall needed"
Not in my experience. Its just a drive throwing a fit.
> 3. I've had it happen on Intel and VIA chipsets alike, 100% guaranteed
> non-overclocked
I've only seen it on broken boards that also needed DMA off in 2.2 and
on the VIA stuff before the VIA fixups went in and the new via driver.
> 5. I have yet to see a coherent explanation from Andre as to what the
> message means, or what causes it.
We issued a DMA, the drive sat their and did nothing. The default handler
asks the controller handling the request to retry it in PIO mode. Which is
readonable. On the 440BX this uses disable_irq which may also trigger a bug
in the APIC on SMP machines and hang solid unless you have -ac. I dont think
thats statistically likely here.
The code looks correct, its a bit convoluted but it does seem to correctly
reissue the request, although not as PIO. Perhaps Andre can explain why its
ignoring the 'please use pio' hint on the return
Alan
-
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/