From: "Dead2" <dead2@circlestorm.org>
To: "Mark Hahn" <hahn@physics.mcmaster.ca>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Asus CUV266-D problems
Date: Sun, 30 Sep 2001 00:24:51 +0200 [thread overview]
Message-ID: <008701c14935$90675530$0500000a@dead2> (raw)
In-Reply-To: <Pine.LNX.4.10.10109281126270.6506-100000@coffee.psychology.mcmaster.ca>
It uses an UDMA-100 certified cable, it is the regular flat type.
80pin, both ends connected, no defects or sharp bends detected.
I have tried 3 _NEW_ cables now, and none of them fixes the problem.
I have also tried 2 disks with the same results.
I have not overclocked, and I run the safest bios config I can think of..
It is also _VERY_ predictable.. It only occurs at that one point during
booting of Linux. (See the logfile attached with the last mail)
I surely don't understand what I have done wrong if anything..
-=Dead2=-
PS: Thanx for any help!
----- Original Message -----
From: "Mark Hahn" <hahn@physics.mcmaster.ca>
To: "Dead2" <dead2@circlestorm.org>
Sent: Friday, 28 September, 2001 5:28 PM
Subject: Re: Asus CUV266-D problems
> > <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> BadCRC can only ever mean that there's signal corruption on the cable
> (detected and retried; harmless if infrequent.) most often, this is
> because your cable is out-of-spec: it must be <= 18", both ends must
> be plugged in, and it must be 80-conductor if you're using > udma33.
> overclocking and badly-designed motherboards can cause this as well;
> "rounded" cables will too, probably, since they trash the cable's
> crosstalk specs.
>
next parent reply other threads:[~2001-09-29 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10109281126270.6506-100000@coffee.psychology.mcmaster.ca>
2001-09-29 22:24 ` Dead2 [this message]
2001-09-28 13:09 Asus CUV266-D problems Dead2
-- strict thread matches above, loose matches on Subject: below --
2001-09-26 15:27 Dead2
[not found] ` <3BB23E0C.B7F708E0@home.com>
[not found] ` <3BB27774.4FA630A2@home.com>
2001-09-27 9:05 ` Dead2
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='008701c14935$90675530$0500000a@dead2' \
--to=dead2@circlestorm.org \
--cc=hahn@physics.mcmaster.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox