When I do that on the DMA-refusing disk (that, BTW does work with DMA on
its own...), I get:
==> /var/log/messages <==
Mar 30 19:38:50 zap kernel: hdc: irq timeout: status=0x58 { DriveReady
SeekComplete DataRequest }
Mar 30 19:38:50 zap kernel: ide1: reset: success
and all accesses to that drive hang, until I do hdparm -d0
...
Thanx for trying to give me a good tip though.
Cya, Jelle.
On Sun, 29 Mar 1998, mlord wrote:
> Jelle Foks wrote:
> >
> > Hello,
> >
> > Hey, I've seen the same kind of effect: On a 430FX with two (regular
> > EIDE-DMA) 4.3GB quantum bigfoots, each on a separate controller cable
> > (hda & hdc).
> >
> > When the system boots, the DMA for one of them (hdc) gets switched off
> > after an IDE interface reset and pause... (kernel 2.0.33 on RH5).
>
> Stick something like this into /etc/rc.d/rc.local:
>
> hdparm -d1 -k1 /dev/hd?
>
> --
> mlord@pobox.com
> The Linux IDE guy
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu