From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 214311] megaraid_sas - no disks detected
Date: Tue, 04 Oct 2022 08:41:54 +0000 [thread overview]
Message-ID: <bug-214311-11613-5vFqM8SPf7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214311-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214311
Sumit Saxena (sumit.saxena@broadcom.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sumit.saxena@broadcom.com
--- Comment #5 from Sumit Saxena (sumit.saxena@broadcom.com) ---
Driver fails to get controller information from controller firmware which leads
to the driver load failure and disks don't get exposed to OS.
It may be the controller firmware problem. Please ensure the latest controller
firmware is flashed. If the issue persists with the latest controller firmware,
please contact Broadcom support channel.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-10-04 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 11:23 [Bug 214311] New: megaraid_sas - no disks detected bugzilla-daemon
2021-09-04 12:33 ` [Bug 214311] " bugzilla-daemon
2021-09-11 18:56 ` [Bug 214311] New: " Salvatore Bonaccorso
2021-09-11 18:56 ` [Bug 214311] " bugzilla-daemon
2021-09-18 7:20 ` bugzilla-daemon
2022-10-03 6:40 ` bugzilla-daemon
2022-10-04 8:41 ` bugzilla-daemon [this message]
2022-10-04 12:51 ` bugzilla-daemon
2022-10-28 9:12 ` bugzilla-daemon
2022-10-31 15:13 ` bugzilla-daemon
2023-12-11 14:11 ` 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-214311-11613-5vFqM8SPf7@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).