Marc Merlin wrote:
>
>While I'll be the last person to praise IDE, recent drives and controllers
>have CRC error checking, which is actually better than parity.
>
OK, maybe this could shed some light on a mystery I'm fighting here with.
I recently replaced this (Asus P55T2P4) motherboard:
---
Oct 22 15:53:45 ruri kernel: PIIX3: IDE controller on PCI bus 00 dev 39
Oct 22 15:53:45 ruri kernel: PIIX3: not 100% native mode: will probe irqs
later
Oct 22 15:53:45 ruri kernel: ide0: BM-DMA at 0xe800-0xe807, BIOS
settings: hda:pio, hdb:pio
Oct 22 15:53:45 ruri kernel: ide1: BM-DMA at 0xe808-0xe80f, BIOS
settings: hdc:pio, hdd:pio
Oct 22 15:53:45 ruri kernel: hda: IBM-DTTA-351680, ATA DISK drive
Oct 22 15:53:45 ruri kernel: hdc: IBM-DTTA-351680, ATA DISK drive
Oct 22 15:53:45 ruri kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct 22 15:53:45 ruri kernel: ide1 at 0x170-0x177,0x376 on irq 15
Oct 22 15:53:45 ruri kernel: hda: IBM-DTTA-351680, 16124MB w/462kB Cache,
CHS=32760/16/63, (U)DMA
Oct 22 15:53:45 ruri kernel: hdc: IBM-DTTA-351680, 16124MB w/462kB Cache,
CHS=32760/16/63, (U)DMA
---
It ran flawlessly and the disks showed no problems running with DMA
and delivering around 10MB/s or more with bonnie.
Now I replaced the motherboard (and nothing else like cables) with a
Tyan Trinity 100AT one:
---
Nov 7 18:25:51 ruri kernel: VP_IDE: IDE controller on PCI bus 00 dev 39
Nov 7 18:25:51 ruri kernel: VP_IDE: not 100% native mode: will probe irqs
later
Nov 7 18:25:51 ruri kernel: ide0: BM-DMA at 0xe000-0xe007, BIOS
settings: hda:DMA, hdb:DMA
Nov 7 18:25:51 ruri kernel: ide1: BM-DMA at 0xe008-0xe00f, BIOS
settings: hdc:DMA, hdd:DMA
Nov 7 18:25:51 ruri kernel: hda: IBM-DTTA-351680, ATA DISK drive
Nov 7 18:25:51 ruri kernel: hdc: IBM-DTTA-351680, ATA DISK drive
Nov 7 18:25:51 ruri kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Nov 7 18:25:51 ruri kernel: ide1 at 0x170-0x177,0x376 on irq 15
Nov 7 18:25:51 ruri kernel: hda: IBM-DTTA-351680, 16124MB w/462kB Cache,
CHS=32760/16/63, UDMA
Nov 7 18:25:51 ruri kernel: hdc: IBM-DTTA-351680, 16124MB w/462kB Cache,
CHS=32760/16/63, UDMA
---
And promptly got this when putting some load on the HDs:
---
Nov 7 17:54:00 ruri kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 7 17:54:00 ruri kernel: hdc: dma_intr: error=0x84 { DriveStatusError
BadCRC }
Nov 7 17:54:00 ruri kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 7 17:54:00 ruri kernel: hda: dma_intr: error=0x84 { DriveStatusError
BadCRC }
---
Turning off UDMA solves the problem and also halves the performance.
My questions are thus:
Did the old chip-set just use DMA (instead of UDMA) and thus didn't
triggers these problems?
If so, any way to put the VIA controller into plain DMA mode?
Or did the old chip-set no CRC checks and thus never noticed these problems?
But that should have caused some corruption and it never occured.
Dewa,
<CB>
--
// <CB> aka Christian Balzer, Tannenstr. 23c, D-64342 Seeheim, Germany
\X/ [EMAIL PROTECTED] | Voice: +49 6257 83036, Fax/Data: +49 6257 83037
SWB - The Software Brewery - | http://www.swb.de/ | Anime no Otaku
