From: Wessel Dankers <wsl@fruit.eu.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: HPT366: DMA errors?
Date: Sat, 23 Feb 2002 14:44:01 +0100 [thread overview]
Message-ID: <20020223144400.D22191@fruit.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.40.0202212304240.438-100000@sartre.linuxbr.com>
In-Reply-To: <Pine.LNX.4.40.0202212304240.438-100000@sartre.linuxbr.com>; from sartre@linuxbr.com on Thu, Feb 21, 2002 at 11:14:11PM -0300
On 2002-02-21 23:14:11-0300, Cesar Suga wrote:
> Hello, all.
>
> I am using an ABIT BP6 board (SMP, 2 Celerons at 366MHz, none
> overclocked, *very* stable) which uses the HPT366 controller. I am getting
> through these messages when using the *original* ATA cable (never touched
> before) or a replacement one:
>
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
I got this very same error on my normal VIA ide controller with every cable
I tried until I figured out that perhaps I should like, actually compile in
the VIA driver :)
Basically, reading would go without problems but writing would give the
above error and make the controller go back to PIO mode access. I agree
that it is most likely a cable problem but I wouldn't rule out the driver a
priori.
--
Wessel Dankers <wsl@fruit.eu.org>
Small animal kamikaze attack on power supplies
next prev parent reply other threads:[~2002-02-23 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 2:14 Cesar Suga
2002-02-22 2:36 ` Alan Cox
2002-02-22 2:55 ` Cesar Suga
2002-02-22 3:02 ` Mike Fedyk
2002-02-22 6:47 ` Cesar Suga
2002-02-23 13:44 ` Wessel Dankers [this message]
2002-02-25 20:06 ` Bill Davidsen
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=20020223144400.D22191@fruit.eu.org \
--to=wsl@fruit.eu.org \
--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
all inboxes | Powered by JetHome®