From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: hardreset on SERR_INTERNAL
Date: Wed, 14 Mar 2007 20:50:31 +0900 [thread overview]
Message-ID: <45F7E187.7040306@gmail.com> (raw)
In-Reply-To: <45F7C0B6.4010205@garzik.org>
Jeff Garzik wrote:
> Tejun Heo wrote:
>> There was a rare report where SB600 reported SERR_INTERNAL and SRST
>> couldn't get it out of the failure mode. Hardreset on SERR_INTERNAL.
>> As the problem is intermittent, whether this fixes the problem or not
>> hasn't been verified yet, but hardresetting the channel on internal
>> error is a good idea anyway.
>
> How does this interact with the patch ATI just posted, which prefers to
> treat the SB600 SERR_INTERNAL differently?
Gee... That looks like the correct fix. Raising SERR_INTERNAL on ATAPI
CC never occurred to me. I still think hardresetting on SERR_INTERNAL
is better than softresetting tho.
--
tejun
next prev parent reply other threads:[~2007-03-14 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 16:20 [PATCH] libata: hardreset on SERR_INTERNAL Tejun Heo
2007-03-14 9:30 ` Jeff Garzik
2007-03-14 11:50 ` Tejun Heo [this message]
2007-04-04 5:43 ` Jeff Garzik
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=45F7E187.7040306@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).