From: Mark Lord <liml@rtr.ca>
To: sr@gimp.org
Cc: Erik Frederiksen <erik_frederiksen@pmc-sierra.com>,
linux-ide@vger.kernel.org
Subject: Re: Errors and resets using sata_promise and libata 1.20
Date: Sat, 15 Jul 2006 09:08:38 -0400 [thread overview]
Message-ID: <44B8E8D6.8020903@rtr.ca> (raw)
In-Reply-To: <20060715065001.GA11832@localnet>
Sven Riedel wrote:
> On Fri, Jul 14, 2006 at 01:31:16PM -0400, Mark Lord wrote:
>>> ata2: status=0x50 { DriveReady SeekComplete }
>>> sdb: Current: sense key=0x0
>>> ASC=0x0 ASCQ=0x0
>> [...]
>> Then the LLD in some cases resets the channel to clear the controller
>> state machine, but this also clears the ERR bit, giving status 0x50
>> (I believe there to be other paths to the same result as well, but have
>> not yet had time to investigate further).
>>
>> Then later in handling of the same failed command, the libata-scsi layer
>> finally has to report the error upstream, but by now it only sees 0x50
>> and has no idea what went wrong.
>
> Is there a patch somewhere that didn't make it into the kernel yet, that we
> can try?
No. And it's quite unfortunate, as this bug prevents proper error handling
by the SCSI layer, since libata doesn't accurately report what problem it saw.
The 2.6.18 libata EH is reputedly much improved, but may still have the same
bug (LLD reads/discards status, requiring libata-core to re-read it again after
it may have changed).
Cheers
next prev parent reply other threads:[~2006-07-15 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 17:29 Errors and resets using sata_promise and libata 1.20 Erik Frederiksen
2006-07-12 18:04 ` Justin Piszcz
2006-07-14 17:31 ` Mark Lord
2006-07-15 6:50 ` Sven Riedel
2006-07-15 13:08 ` Mark Lord [this message]
2006-07-15 13:20 ` Sven Riedel
2006-07-15 13:31 ` Greg Freemyer
2006-07-16 7:13 ` Sven Riedel
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=44B8E8D6.8020903@rtr.ca \
--to=liml@rtr.ca \
--cc=erik_frederiksen@pmc-sierra.com \
--cc=linux-ide@vger.kernel.org \
--cc=sr@gimp.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;
as well as URLs for NNTP newsgroup(s).