Skip to contentSkip to conversation

ide / usb problem

DISCUSSION Fr�d�ric L. W. Meunier 8 participants 8 messages Feb 25, 2001 – Feb 27, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 9 lines · Alan Cox
Quoted 6 lines

I was not sure if the VIA82CXXX option should be set with the via kt133 chipset , but setting it results in hundreds of
hda: dma_intr:status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr:error=0x84 { DriveStatusError BadCRC } mesages along with the uhci: errors mentioned above. Again , the directory was copied correctly.

That indicates cable problems. The CRC will avoid bad transfers as it will do retries

Oh my god. Are you sure it's a cable problem? I'm using the cable shipped by ASUS with my K7V and have the same problem:

devfs: v0.102 (20000622) Richard Gooch ([email protected])
devfs: boot_options: 0x2
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

Again, if it's really a cable problem, then ASUS is selling cables that don't work with UDMA66 (but they sell it as UDMA66).

I urge ASUS to explain this problem. If you do a search for BadCRC at any lkml archive, you should notice most complaints are from... VIA (and most seem to have an ASUS motherboard).

Signature · 1 line
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
#1 lore raw
Quoted 2 lines · In article <20010225060326.K127@pervalidus> you wrote:

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

I think I saw that with broken Drives, too.

Greetings
Bernd

#2 lore raw
In reply to Fr�d�ric L. W. Meunier
Quoted 7 lines

hda: dma_intr: status=3D0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=3D0x84 { DriveStatusError BadCRC }
ide0: reset: success

Again, if it's really a cable problem, then ASUS is selling cables that don't work with UDMA66 (but they sell it as UDMA66).

To get ATA66 working well you need the right cables, you also need a machine that is to spec on interference and the like. You cant just point at the cables althoigh they are first guess.

#7 lore raw
In reply to Fr�d�ric L. W. Meunier

I also am using the cable supplied with the mobo (Abit kt7) so I do not think it is ASUS specific. More likey it is releated to the VIA chipset and/or driver.

If I compile kernel with "Generic PCI bus-master DMA support" and run "hdparm -d1 /dev/hda" I get 700% performance increase on hdparm -t benchmark and I do not get any dma BadCRC errors.

It is only when I also compile in the VIA82CXXX option that I get the

    "hda: dma_intr:status=0x51 { DriveReady SeekComplete Error }"
    "hda: dma_intr:error=0x84 { DriveStatusError BadCRC }"

mesages (1000's of them).

Whether I get the messages or not, if I have dma enabled with 2.4.2 my usb mouse stops working .

jpd

Quoted 29 lines
Quoted 3 lines

That indicates cable problems. The CRC will avoid bad transfers as it will do retries

Oh my god. Are you sure it's a cable problem? I'm using the cable shipped by ASUS with my K7V and have the same problem:

devfs: v0.102 (20000622) Richard Gooch ([email protected])
devfs: boot_options: 0x2
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

Again, if it's really a cable problem, then ASUS is selling cables that don't work with UDMA66 (but they sell it as UDMA66).

I urge ASUS to explain this problem. If you do a search for BadCRC at any lkml archive, you should notice most complaints are from... VIA (and most seem to have an ASUS motherboard).

Signature · 1 line
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
#3 lore raw
In reply to Alan Cox
Quoted 4 lines · Alan Cox
Quoted 4 lines

hda: dma_intr: status=3D0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=3D0x84 { DriveStatusError BadCRC }
ide0: reset: success

Quoted 8 lines
Quoted 3 lines

Again, if it's really a cable problem, then ASUS is selling cables that don't work with UDMA66 (but they sell it as UDMA66).

To get ATA66 working well you need the right cables, you also need a machine that is to spec on interference and the like. You cant just point at the cables althoigh they are first guess.

I have a similar setup and had the same problems. Dump your cables and get ATA/100 Certified cables and you should not have this problem. Also keep the cable length in mind. Anybody out there know if there's a max cable length for the ATA/100 spec??

Quoted 5 lines

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

- - -
Jasmeet Sidhu
Unix Systems Administrator
ArrayComm, Inc.
[email protected]
www.arraycomm.com

#4 lore raw
Quoted 2 lines

the cable length in mind. Anybody out there know if there's a max cable length for the ATA/100 spec??

18", like *all* ide/ata cables.

#5 lore raw
In reply to Jasmeet Sidhu
Quoted 4 lines · Mark Hahn
Quoted 2 lines

the cable length in mind. Anybody out there know if there's a max cable length for the ATA/100 spec??

18", like *all* ide/ata cables.

Actually the ATA/66 and ATA/100 cables are specified to be exactly 18", not longer, not shorter.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs
#6 lore raw
Quoted 8 lines · Vojtech Pavlik
Quoted 4 lines · Mark Hahn
Quoted 2 lines

the cable length in mind. Anybody out there know if there's a max cable length for the ATA/100 spec??

18", like *all* ide/ata cables.

Actually the ATA/66 and ATA/100 cables are specified to be exactly 18", not longer, not shorter.

Not exactly the case, but I do not want to cause more headaches by showing the method of variation that will work in many cases. Thus 45cm or 18" will do..

Cheers,

Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------

ASL, Inc.                                     Toll free: 1-877-ASL-3535
1757 Houret Court                             Fax: 1-408-941-2071
Milpitas, CA 95035                            Web: www.aslab.com