Hi!
> > > Sep 21 23:55:44 fs1 kernel: hdb: timeout waiting for DMA
> > > Sep 21 23:55:44 fs1 kernel: hdb: irq timeout: status=0xd0 { Busy }
> > > Sep 21 23:55:44 fs1 kernel: hda: DMA disabled
>
> Perhaps some timeouts are not set correctly or the specs include some errors, but
> it is very strange behaviour, that with kernel 2.0.36 there was never such a problem
> with heavy loaded systems and after switching to 2.2.16 / 2.2.17 the system dies
> after a short time!!!
>
> I would like to help if i can, but i'm no kernel developer; all i can do is to provide
> a very heavy loaded machine (video-sequencing) with three different drives.
> I hope they haven't been destroyed by the driver, but i'm sure the drivers behaviour
> let them think they have large amounts of bad blocks.
Large ammounts of bad blocks? So you do have hw problem after all.
If software than provoke your disks to think they have bad blocks, your
disks a certainly broken. [There may be another error somewhere in linux,
but theres at least one error in the hw.]
Pavel
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Sep 30 2000 - 21:00:18 EST