VIA VT82C686X
Me too. But I couldn't get UDMA 66 after changing my BIOS settings and booting. With 33 it's very stable (what I used with 2.4.0). A diff:
-hda: 30015216 sectors (15368 MB) w/2048KiB Cache, CHS=1868/255/63, UDMA(33) +hda: 30015216 sectors (15368 MB) w/2048KiB Cache, CHS=1868/255/63, UDMA(66)
...
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
VFS: Mounted root (ext2 filesystem) readonly.
-Freeing unused kernel memory: 200k freed
+Freeing unused kernel memory: 204k freed
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+ide0: reset: success
I know this is a known issue, but I thought testing would be OK. ASUS K7V with the shipped cable.
Signature · 5 lines
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/You system did something funny or the new VIA code did it. But because you observed this pattern the new feature that on Linux has kicked in and hopefull recovered the system for you.
Quoted 11 lines · On Wed, 31 Jan 2001, [iso-8859-1] Fr�d�ric L. W. Meunier wrote:
Me too. But I couldn't get UDMA 66 after changing my BIOS settings and booting. With 33 it's very stable (what I used with 2.4.0). A diff:
(quoted diff) +3
-1-hda: 30015216 sectors (15368 MB) w/2048KiB Cache, CHS=1868/255/63, UDMA(33) +hda: 30015216 sectors (15368 MB) w/2048KiB Cache, CHS=1868/255/63, UDMA(66) +hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC }VFS: Mounted root (ext2 filesystem) readonly.
(quoted diff) +0
-1-Freeing unused kernel memory: 200k freed
Review
Quoted 10 lines
(quoted diff) +10
-0+Freeing unused kernel memory: 204k freed +hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC } +hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC } +hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC } +hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } +hda: dma_intr: error=0x84 { DriveStatusError BadCRC } +ide0: reset: success
Because you did not see DMA_DISABLED
The auto_dma_crc downgrade feature turned down the transfer rate of the drive/host pair until the iCRC issue stablized.
Cheers,
Quoted 10 lines
I know this is a known issue, but I thought testing would be OK. ASUS K7V with the shipped cable.
Signature · 5 lines
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niter�i-RJ BR) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Andre Hedrick
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/