How's the nforce4 support in Linux?
Quoted 5 lines · Julien Wajsberg
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60 Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {DriveReady SeekComplete DataRequest }
Quoted 8 lines
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command(something) like the same problem here:
I get lots of:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
The disk (WDC WD800JB) is about 1/2 year old.
I've checked the drive in my old system... nothing!
Also WD's diagnostic kit doesn't report any problems like bad sectors, or other troubles...
(Please CC me, I'm not on the list)
`
Quoted 2 lines
hda:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda:dma_intr: error=0x84 { DriveStatusError BadCRC
BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a cable used at too high a speed for the cable.
Quoted 6 lines · Arjan van de Ven
`
Quoted 2 lines
hda:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda:dma_intr: error=0x84 { DriveStatusError BadCRCBadCRC is 99% sure a cabling issue; either a bad/overheated cable or a cable used at too high a speed for the cable.
No. It is more likely that the timing programming between the disk and host controller are in a miss-match state. UDMA mode detection can come in to mind too. It makes sense to experiment with hdparm to see if the problem goes away in non Ultra DMA modes.
Quoted 9 lines · Marcin Dalecki
Quoted 7 lines · Arjan van de Ven
`
Quoted 2 lines
hda:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda:dma_intr: error=0x84 { DriveStatusError BadCRCBadCRC is 99% sure a cabling issue; either a bad/overheated cable or a cable used at too high a speed for the cable.
Quoted 6 lines
No. It is more likely that the timing programming between the disk and host controller
are in a miss-match state. UDMA mode detection can come in to mind too. It makes sense to experiment with hdparm to see if the problem goes away in non
Ultra DMA modes.
Thanks, I tried the cable that came with the drive (it was still sealed) and experimented a little bit with hdparm...
Now, the problem seems to be gone...
Quoted 10 lines · Marcin Dalecki
Quoted 6 lines · Arjan van de Ven
`
Quoted 2 lines
hda:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda:dma_intr: error=0x84 { DriveStatusError BadCRCBadCRC is 99% sure a cabling issue; either a bad/overheated cable or a cable used at too high a speed for the cable.
Quoted 6 lines
No. It is more likely that the timing programming between the disk and host controller
are in a miss-match state. UDMA mode detection can come in to mind too. It makes sense to experiment with hdparm to see if the problem goes away in non
Ultra DMA modes.
Do you mean "multiword dma modes" or "pio modes" ?
Signature · 1 line
Julien