From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 219330] New: mpt3sas add 1000:009f Device ID as SAS9300-4i4e
Date: Fri, 27 Sep 2024 18:37:09 +0000 [thread overview]
Message-ID: <bug-219330-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219330
Bug ID: 219330
Summary: mpt3sas add 1000:009f Device ID as SAS9300-4i4e
Product: SCSI Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Other
Assignee: scsi_drivers-other@kernel-bugs.osdl.org
Reporter: me@ndoo.sg
Regression: No
I have an LSI 9300-4i4e that identifies with ven/dev ID as follows,
```
# lspci -nnv
[snip]
0004:01:00.0 Mass storage controller [0180]: Broadcom / LSI Device [1000:009f]
(rev 02)
Flags: fast devsel, IRQ 379, IOMMU group 9
I/O ports at 10000 [disabled] [size=256]
Memory at a400000000 (64-bit, non-prefetchable) [disabled] [size=64K]
Expansion ROM at a040000000 [disabled] [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, IntMsgNum 0
Capabilities: [d0] Vital Product Data
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable- Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] Secondary PCI Express
Capabilities: [1c0] Power Budgeting <?>
Capabilities: [190] Dynamic Power Allocation <?>
Capabilities: [150] Single Root I/O Virtualization (SR-IOV)
Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
```
It seems like most 4i4e cards identify with device ID 0x0097 and I am not sure
why this card from the resale market identifies as 0x009f. However all visible
labels indicate it is a legitimate 4i4e card.
I was able to update the card firmware to P16 release for LSI 9300-4i4e from
the Broadcom website using sas3flsh.exe from DOS.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2024-09-27 18:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-219330-11613@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