From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 13594] SMART responses for SATA disks on SAS get interpreted as errors
Date: Sun, 21 Jun 2009 21:14:38 GMT [thread overview]
Message-ID: <200906212114.n5LLEcR2011098@demeter.kernel.org> (raw)
In-Reply-To: <bug-13594-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13594
--- Comment #6 from Steinar H. Gunderson <sgunderson@bigfoot.com> 2009-06-21 21:14:37 ---
On Sun, Jun 21, 2009 at 08:53:37PM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> I have just replicated the "ATA pass through information
> available" message report on a similar vintage LSI
> controller and a SATA disk with a recent smartctl
> version.
>
> There is no need to report this in the kernel error log,
> as the smartmontools ATA pass-through (SCSI) command asked
> for the final state of the ATA registers and the sense
> buffer is the conduit for that information. That ASC/ASCQ
> pair basically means "you asked for them and here they
> are". [reference: sat2r07b.pdf section 12.2.5 table 107
> when CK_COND is 1]
OK, this is basically what we agreed on already. I'm not able to
test the given patch right now, though (the machine is a production
machine).
> As for the hiccup, I have noticed that with SAS (SCSI)
> disks from Seagate there is a curious sound and a pause
> before the response to LOG SENSE SCSI command (the
> type the smartmontools uses on SCSI disks).
FWIW, I've used the same disks on SATA controllers with smartctl
without any problems. I'm not entirely sure how to parse your
message, though -- do you imply that the problem is in smartctl?
The disk?
/* Steinar */
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2009-06-21 21:14 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
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 [this message]
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=200906212114.n5LLEcR2011098@demeter.kernel.org \
--to=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).