--- civileme <[EMAIL PROTECTED]> wrote:
...
> 3. Setting DMA on some systems (and this happens on so few that we have
> little data) simply does not work for one or more drives, and we have a
> partition check that hangs the system. It might be related to a CDRW or to a
>
> Promise ATA/66 Controller. More data is welcome. Particularly welcome is
> any data of anyone able to reproduce this error _without_ WD drives.
> Unfortunately, this brand seems to be a factor in the failures, and it does
> have hardware differences from other drives. One empirical factor is that
> setting idex=noautotune sometimes stops this behavior (where x is the
> offending channel).
I just installed 2.4.1-15mdk and 2.2.18-13mdk and 2.4.1 work, but 2.2.18 does
not.
What I don't understand is, that if it is related to WD drives then why does it
happens to only one drive, when I have other WD drives of the same model
before (hda & hdb) the one that caused the DMA timeout. And if it is the drive
brand, then why does it happens with one kernel and not the other, 2.2.16-9mdk
works, but 2.2.18-13mdk does not; I guess there is a WD workaround in the ide
driver, that is being moved around, since I am constantly trying out new
kernels, and with some version it works, and with the next it goes back to not
working (specially with the 2.4 series, with the 2.2 it has never work after
2.2.16-9mdk).
=====
________________________
Eugenio Diaz, BSEE/BSCE
Linux Engineer
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
