From: "Peter" <sw98234@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: wrt: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Date: Sat, 26 Aug 2006 17:41:53 +0000 (UTC) [thread overview]
Message-ID: <ecq151$9t3$2@sea.gmane.org> (raw)
In-Reply-To: ecpru4$9t3$1@sea.gmane.org
On Sat, 26 Aug 2006 16:12:52 +0000, Peter wrote:
> Using 2.6.17.11 with reiser4 patch only. Voluntary preempt.
>
> Recently, I have been receiving this sequence of errors:
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> ide: failed opcode was: unknown
snip....
I should mention that I have an 80 pin IDE cables, and did try replacing
it. Same result. This problem is new, so I do not believe the cable is the
issue -- esp since manu diags show all is well.
--
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via
jabber: pete4abw at jabber.org
ICQ: 73676357
next prev parent reply other threads:[~2006-08-26 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-26 16:12 wrt: dma_intr: status=0x51 { DriveReady SeekComplete Error } Peter
2006-08-26 17:41 ` Peter [this message]
2006-08-26 22:46 ` Alan Cox
2006-08-27 7:11 ` Rogier Wolff
2006-08-27 10:49 ` Peter
2006-08-27 17:44 ` RESOLVED: " Peter
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='ecq151$9t3$2@sea.gmane.org' \
--to=sw98234@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox