On Fri, 22 Sep 2000, Alan Cox wrote:
> > This machine is running 2.2.17aa2 (I needed LFS), and I'm able to lock it
> > hard. This is what was in the logs :
> >
> > Sep 21 23:55:38 fs1 kernel: hdc: dma_intr: status=0x51 { DriveReady
> > SeekComplete Error }
>
> A disk seek failed
>
> > Sep 21 23:55:38 fs1 kernel: hdc: dma_intr: error=0x40 { UncorrectableError
> > }, LBAsect=16373421, sector=3521368
>
> Uncorrectable error is the drive.
No, that's not the case. If it md5sum the file one at a time, all is fine.
Both disks are brand new, so I doubt a hardware failure on the disk side..
It could be that it is choking on the fact that one drives is LBA, one
drive isn't. Drives are identical, but dmesg gives different CHS for each
of them..
> > 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
> > Sep 21 23:55:44 fs1 kernel: hdb: DMA disabled
> > Sep 21 23:55:44 fs1 kernel: ide0: unexpected interrupt, status=0xd0,
> > count=1
> > Sep 21 23:55:44 fs1 kernel: ide0: reset: success
>
> Then it tried an IDE reset, then it choked
Why the total meltdown ?
Igmar
-
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 23 2000 - 21:00:26 EST