public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 106841] ses: do not output error for simple subenclosure (handle Short Enclosure Status diagnostic page)
Date: Sat, 27 Feb 2016 01:21:39 +0000	[thread overview]
Message-ID: <bug-106841-11613-Tljg8seZsR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106841-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=106841

--- Comment #2 from Tom Yan <tom.ty89@gmail.com> ---
This commit did NOT fix anything:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=3417c1b5cb1fdc10261dbed42b05cc93166a78fd

Only the error changes from:

scsi 7:0:0:1: Failed to get diagnostic page 0x8000002
scsi 7:0:0:1: Failed to bind enclosure -19

to

scsi 7:0:0:1: Wrong diagnostic page; asked for 1 got 0
scsi 7:0:0:1: Failed to get diagnostic page 0xffffffea
scsi 7:0:0:1: Failed to bind enclosure -19

The ses driver should simply check whether there is an Short Enclosure Status
page (i.e. it is a simple subenclosure) FIRST. If that's the case, the device
should simply be skipped/bound WITHOUT error.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2016-02-27  1:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  4:26 [Bug 106841] New: do not output error for simple subenclosure (handle Short Enclosure Status diagnostic page) bugzilla-daemon
2015-10-29  4:27 ` [Bug 106841] " bugzilla-daemon
2016-02-27  1:13 ` [Bug 106841] ses: " bugzilla-daemon
2016-02-27  1:13 ` bugzilla-daemon
2016-02-27  1:21 ` bugzilla-daemon [this message]

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=bug-106841-11613-Tljg8seZsR@https.bugzilla.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