Messages in this thread | | | Subject | Re: Linux 2.4.25-pre7 - no DRQ after issuing WRITE | From | "Gabor Z. Papp" <> | Date | Sun, 25 Jan 2004 20:33:02 +0100 |
| |
* Marcelo Tosatti <marcelo.tosatti@cyclades.com>:
| > Here we go: http://gzp.odpn.net/tmp/linux-2.4.25-pre7/ | > | > The "no DRQ after issuing WRITE" problem with 2 120GB Seagate
...
| I'm not IDE expert, but these errors look like hardware fault for me | (Bartlomiej CCed). | | What about 2.6 and older 2.4 kernels on the same hardware ?
Same kernel works fine in a non-sw-raid environment, when I can't stress enough the harddisks to fail. When I boot NetBSD 1.6.1, I'm able to read-write the disks nonstop without any error. Thats why I think its not hw problem, but I would like to use Linux 2.4, so I'm waiting for Bartlomiej.
| ------------- | Mounted devfs on /dev | Freeing unused kernel memory: 116k freed | hde: dma_timer_expiry: dma status == 0x21 | hdg: dma_timer_expiry: dma status == 0x21 | hde: error waiting for DMA | hde: dma timeout retry: status=0x7f { DriveReady DeviceFault SeekComplete | DataRequest CorrectedError Index Error } | hde: dma timeout retry: error=0x7f { DriveStatusError UncorrectableError | SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, | LBAsect=9343692930943, high=556927, low=8355711, sector=4352 | hde: DMA disabled | hdg: error waiting for DMA | hdg: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest | } | hdg: status error: status=0x50 { DriveReady SeekComplete } | hdg: no DRQ after issuing MULTWRITE | hdg: status timeout: status=0xd0 { Busy }
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |