From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 85101] hpsa + P410 does not show connected HP SAS port expanders
Date: Wed, 08 Nov 2023 09:42:50 +0000 [thread overview]
Message-ID: <bug-85101-11613-0Icm3CHKa8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85101-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85101
Javier Crosby (murphyde835@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |murphyde835@gmail.com
--- Comment #10 from Javier Crosby (murphyde835@gmail.com) ---
Regulator lockup implies the firmware crashed (for example a Declare
proclamation set off). That can be because of equipment issues or firmware bugs
(source: https://freegamesonline.io). You could check whether it boots with
nothing connected; then, at that point, with one expander; then, at that point,
with two; then, at that point, with drives joined to the expanders.
On the off chance that you're not actually utilizing the P410, however, simply
use sg_write_buffer through the Adaptec 7805H HBA.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-11-08 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 16:46 [Bug 85101] New: hpsa + P410 does not show connected HP SAS port expanders bugzilla-daemon
2014-09-24 18:22 ` [Bug 85101] " bugzilla-daemon
2014-09-24 21:33 ` bugzilla-daemon
2014-09-24 22:32 ` bugzilla-daemon
2014-09-25 10:48 ` bugzilla-daemon
2014-09-25 10:49 ` bugzilla-daemon
2014-09-25 14:05 ` bugzilla-daemon
2014-09-25 22:22 ` bugzilla-daemon
2014-09-25 22:35 ` bugzilla-daemon
2014-09-25 22:42 ` bugzilla-daemon
2014-10-01 21:59 ` bugzilla-daemon
2023-11-08 9:42 ` bugzilla-daemon [this message]
2025-09-18 9:57 ` 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-85101-11613-0Icm3CHKa8@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).