From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org, "Moore, Eric" <Eric.Moore@lsi.com>
Subject: Re: [Bug 13594] SMART responses for SATA disks on SAS get interpreted as errors
Date: Sun, 21 Jun 2009 14:07:08 -0500 [thread overview]
Message-ID: <1245611228.4328.239.camel@mulgrave.site> (raw)
In-Reply-To: <200906211858.n5LIwS5j027520@demeter.kernel.org>
On Sun, 2009-06-21 at 18:58 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13594
>
>
>
>
>
> --- Comment #3 from Steinar H. Gunderson <sgunderson@bigfoot.com> 2009-06-21 18:58:28 ---
> (In reply to comment #1)
> > This is a message the kernel prints out on all recovered error returns
> > (except those marked REQ_QUIET). It's purely informational and doesn't
> > affect return processing of the command at all, so the kernel is
> > actually treating this as a successful completion not an error.
>
> OK.
>
> > So this sounds like the bug ... however, for the LSI card, this bug will
> > be in the SAT layer in the fusion firmware. I can shut the kernel up by
> > making the recovered error processing clause look for 01/00/1D as well
> > as REQ_QUIET, but it won't affect this problem.
>
> I tried reporting this to the Linux fusionmpt driver people a while ago, but
> never received any response (thus this bug)... I guess I'm out of luck,
OK, cc'd LSI people, let's see if I get better luck
> then,
> if there's nothing that can be done for it in the kernel. It's a bit weird,
> though; one would believe people ran smartd on their systems and discovered
> this already.
I can guess that it's some type of firmware mode problem: either it runs
for SMART or it runs for normal commands, hence the hiatus. If that's
true, you'd likely only see the problem in a large disk setup ... it
might also be possible to work around by simply quiescing the card
before sending down SMART commands (that would be grossly inefficient,
but at least devices wouldn't get errored).
James
next prev parent reply other threads:[~2009-06-21 19:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 17:26 [Bug 13594] New: SMART responses for SATA disks on SAS get interpreted as errors bugzilla-daemon
2009-06-21 18:47 ` James Bottomley
2009-06-21 18:55 ` James Bottomley
2009-06-21 18:48 ` [Bug 13594] " bugzilla-daemon
2009-06-21 18:55 ` bugzilla-daemon
2009-06-21 18:58 ` bugzilla-daemon
2009-06-21 19:07 ` James Bottomley [this message]
2009-06-21 19:07 ` bugzilla-daemon
2009-06-21 20:53 ` Douglas Gilbert
2009-06-22 12:04 ` Matthew Wilcox
2009-06-21 20:53 ` bugzilla-daemon
2009-06-21 21:14 ` bugzilla-daemon
2009-06-22 12:04 ` bugzilla-daemon
2009-11-21 0:20 ` bugzilla-daemon
[not found] <bug-13594-11613@https.bugzilla.kernel.org/>
2010-04-03 22:07 ` bugzilla-daemon
2010-04-27 22:31 ` bugzilla-daemon
2010-05-01 4:45 ` bugzilla-daemon
2010-05-12 14:09 ` bugzilla-daemon
2010-05-12 14:43 ` Douglas Gilbert
2010-05-12 15:20 ` bugzilla-daemon
2010-05-12 17:42 ` bugzilla-daemon
2010-05-12 17:43 ` bugzilla-daemon
2010-05-18 15:04 ` bugzilla-daemon
2010-07-20 20:08 ` bugzilla-daemon
2010-10-29 3:30 ` bugzilla-daemon
2012-06-08 15:40 ` bugzilla-daemon
2012-06-08 15:40 ` bugzilla-daemon
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=1245611228.4328.239.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=Eric.Moore@lsi.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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).