Messages in this thread | | | Date | Sun, 2 Jul 2000 16:33:53 -0700 (PDT) | From | Andre Hedrick <> | Subject | Re: 2.4.0-test2-ac2 FAT oops |
| |
Samuli,
This is a bad skew in the timing between the drive, cable, host. I forgot the hardware you have but if it has a hwif->speedproc then we are in good shape for it to auto down-grade the transfer to a stable point were the iCRC errors stop.
On Sun, 2 Jul 2000, Samuli Kaski wrote:
> On Fri, 30 Jun 2000, Andre Hedrick wrote: > > > This does fix the possible race condition of double interrupts on the same > > card. > > 2.4.0-test3-pre2 + ide.2.4.0-t3-2.0629 > > Jul 1 15:34:07 vortex kernel: hdf: dma_intr: status=0x51 { DriveReady SeekComplete Error } > Jul 1 15:34:07 vortex kernel: hdf: dma_intr: error=0x84 { DriveStatusError BadCRC } > Jul 1 15:34:07 vortex kernel: hdf: dma_intr: status=0x51 { DriveReady SeekComplete Error } > Jul 1 15:34:07 vortex kernel: hdf: dma_intr: error=0x84 { DriveStatusError BadCRC } > > .. > > Can't reproduce the FAT oops because I can't run the kernel in question > for long periods of time. It doesn't compile all my modules and I don't
What do you mean that it will not run for a long period of time? DeadLock?
> have the time right now to find out why. > > Samuli > >
Andre Hedrick The Linux ATA/IDE guy
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |