From: Frédéric L. W. Meunier <0@pervalidus.net>
To: jerry <jdinardo@ix.netcom.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ide / usb problem
Date: Sun, 25 Feb 2001 06:03:26 -0300 [thread overview]
Message-ID: <20010225060326.K127@pervalidus> (raw)
Alan Cox wrote:
>> 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 (rgooch@atnf.csiro.au)
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).
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
next reply other threads:[~2001-02-25 9:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 9:03 Frédéric L. W. Meunier [this message]
2001-02-25 10:31 ` ide / usb problem Bernd Eckenfels
2001-02-25 13:56 ` Alan Cox
2001-02-25 19:22 ` jerry
2001-02-26 19:53 ` Jasmeet Sidhu
2001-02-26 20:23 ` Mark Hahn
2001-02-27 8:02 ` Vojtech Pavlik
2001-02-27 13:10 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2001-02-26 19:18 David Balazic
2001-02-26 20:06 ` jerry
2001-02-24 12:30 jerry
2001-02-24 16:55 ` Alan Cox
2001-02-25 21:06 ` Tim Moore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010225060326.K127@pervalidus \
--to=0@pervalidus.net \
--cc=jdinardo@ix.netcom.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.