From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 85151] pm80xx + 7805H + HP SAS port expander = mpi_smp_completion 2604:smp IO status 0x2 and sas: expander ... discovery failed(0xffffffa6)
Date: Thu, 25 Sep 2014 16:06:52 +0000 [thread overview]
Message-ID: <bug-85151-11613-UxeI9zYBmu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85151-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #5 from linux-ide@crashplan.pro ---
Yes, the expander has new firmware (v. 2.10 available since early September).
Although my guess is that a firmware upgrade will not be possible as long as
the SAS HBA has an address (a.k.a. initiator port identifier) of 0:
# lsscsi -Ht | grep pm80xx
[4] pm80xx sas:0x0000000000000000
# ls /dev/bsg/ex*
ls: cannot access /dev/bsg/ex*: No such file or directory
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-09-25 16:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 14:44 [Bug 85151] New: pm80xx + 7805H + HP SAS port expander = mpi_smp_completion 2604:smp IO status 0x2 and sas: expander ... discovery failed(0xffffffa6) bugzilla-daemon
2014-09-25 15:05 ` [Bug 85151] " bugzilla-daemon
2014-09-25 15:26 ` bugzilla-daemon
2014-09-25 15:33 ` bugzilla-daemon
2014-09-25 15:53 ` bugzilla-daemon
2014-09-25 16:06 ` bugzilla-daemon [this message]
2014-09-25 16:20 ` bugzilla-daemon
2014-09-26 8:33 ` Jack Wang
2014-09-26 8:34 ` bugzilla-daemon
2014-09-26 9:03 ` bugzilla-daemon
2014-09-26 10:16 ` bugzilla-daemon
2014-09-30 10:27 ` bugzilla-daemon
2014-10-10 21:11 ` bugzilla-daemon
2014-10-10 21:32 ` bugzilla-daemon
2014-10-10 22:00 ` bugzilla-daemon
2014-10-14 16:33 ` bugzilla-daemon
2014-10-19 12:17 ` bugzilla-daemon
2014-10-19 12:18 ` 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=bug-85151-11613-UxeI9zYBmu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.