From: Mark Lord <liml@rtr.ca>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
jgarzik@pobox.com
Subject: Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
Date: Tue, 20 Jun 2006 09:01:59 -0400 [thread overview]
Message-ID: <4497F1C7.2070007@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.64.0606200808250.5851@p34.internal.lan>
Justin Piszcz wrote:
>
> Should someone comment this code out that produces the printk()'s as
> these are useless information as there is no problem with the disk?
MMm.. probably "barrier" commands that the drive doesn't like.
Pity those messages don't also dump the failed opcode.
> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
> DriveStatusError }
> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
> DriveStatusError }
> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense translation
> for status: 0x51
> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense translation
> for status: 0x51
> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense translation
> for status: 0x51
> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
next prev parent reply other threads:[~2006-06-20 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 12:17 LibPATA/ATA Errors Continue - Will there be a fix for this? Justin Piszcz
2006-06-20 13:01 ` Mark Lord [this message]
2006-06-20 13:03 ` Justin Piszcz
2006-06-20 14:23 ` David Greaves
2006-06-20 15:45 ` David Greaves
2006-06-20 15:46 ` Justin Piszcz
2006-06-20 22:20 ` David Greaves
2006-06-20 22:22 ` Justin Piszcz
2006-06-21 11:39 ` Justin Piszcz
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 15:15 Al Boldi
2006-06-20 15:48 ` Justin Piszcz
2006-06-20 16:25 ` Mark Lord
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=4497F1C7.2070007@rtr.ca \
--to=liml@rtr.ca \
--cc=jgarzik@pobox.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.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 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.