From: jurriaan <thunder7@xs4all.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jurriaan <thunder7@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: often ide errors on amd64 / A8N-SLI
Date: Thu, 21 Jul 2005 21:42:40 +0200 [thread overview]
Message-ID: <20050721194240.GA30389@amd64.of.nowhere> (raw)
In-Reply-To: <1121974214.19424.22.camel@localhost.localdomain>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Thu, Jul 21, 2005 at 08:30:13PM +0100
> On Iau, 2005-07-21 at 19:26 +0200, jurriaan wrote:
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> There was corruption on the cable between the controller and drive. That
> usually indicates a cable or noise problem in the PC but could indicate
> mistuning of the interface. Make sure the IDE cable is
>
> [controller]<---- long section ----->[slave]--short section-->[master]
>
> as one common cause is having the cable the other way around.
The cable happens to run the correct way, but you've given me a valuable
hint. I was wondering why hda had errors and hdc (which is the same
drive on the second port of the controller) didn't. Perhaps I'll try
another cable.
Thanks,
Jurriaan
--
IF MICROSOFT BUILT CARS......
You could only have one person in the car at a time, unless you
bought "Car95" or "CarNT". But, then you would have to buy more
seats.
Debian (Unstable) GNU/Linux 2.6.13-rc3-mm1 5149 bogomips load 1.94
next prev parent reply other threads:[~2005-07-21 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 17:26 jurriaan
2005-07-21 19:30 ` Alan Cox
2005-07-21 19:42 ` jurriaan [this message]
2005-07-22 12:47 ` Erik Mouw
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=20050721194240.GA30389@amd64.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome