From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 209177] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:10791/_scsih_probe()!
Date: Sat, 22 Jun 2024 11:49:07 +0000 [thread overview]
Message-ID: <bug-209177-11613-zrh6o2oM1j@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209177-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209177
--- Comment #9 from Guido Serra (zeph@fsfe.org) ---
maybe worth adding the whole dmesg entries for such:
mpt3sas version 43.100.00.00 loaded
mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (32779040 kB)
mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
mpt2sas_cm0: MSI-X vectors supported: 1
mpt2sas_cm0: 0 1 1
mpt2sas_cm0: High IOPs queues : disabled
mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 100
mpt2sas_cm0: iomem(0x00000000e2540000), mapped(0x00000000dddd21ca), size(16384)
mpt2sas_cm0: ioport(0x000000000000e000), size(256)
mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
mpt2sas_cm0: scatter gather: sge_in_main_msg(1), sge_per_chain(9),
sge_per_io(128), chains_per_io(15)
mpt2sas_cm0: request pool(0x000000004246b71a) - dma(0xfed80000): depth(3492),
frame_size(128), pool_size(436 kB)
mpt2sas_cm0: sense pool(0x00000000333696a2) - dma(0xcfa80000): depth(3367),
element_size(96), pool_size (315 kB)
mpt2sas_cm0: reply pool(0x00000000eef15715) - dma(0xcfa00000): depth(3556),
frame_size(128), pool_size(444 kB)
mpt2sas_cm0: config page(0x000000009bf3e151) - dma(0xcf9fb000): size(512)
mpt2sas_cm0: Allocated physical memory: size(7579 kB)
mpt2sas_cm0: Current Controller Queue Depth(3364),Max Controller Queue
Depth(3432)
mpt2sas_cm0: Scatter Gather Elements per IO(128)
mpt2sas_cm0: overriding NVDATA EEDPTagMode setting
mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03),
BiosVersion(00.00.00.00)
mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot
Buffer,Diag Trace Buffer,Task Set Full,NCQ)
mpt2sas_cm0: sending port enable !!
mpt2sas_cm0: hba_port entry: 00000000319a47bc, port: 255 is added to hba_port
list
mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b002c8f75a), phys(8)
mpt2sas_cm0: port enable: SUCCESS
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-22 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-209177-11613@https.bugzilla.kernel.org/>
2020-09-29 19:59 ` [Bug 209177] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:10791/_scsih_probe()! bugzilla-daemon
2020-09-29 20:00 ` bugzilla-daemon
2020-09-30 19:03 ` bugzilla-daemon
2020-09-30 19:04 ` bugzilla-daemon
2021-04-11 7:43 ` bugzilla-daemon
2022-01-03 0:42 ` bugzilla-daemon
2023-10-09 8:29 ` bugzilla-daemon
2024-06-22 11:32 ` bugzilla-daemon
2024-06-22 11:49 ` bugzilla-daemon [this message]
2024-07-02 8:09 ` bugzilla-daemon
2024-07-02 8:55 ` bugzilla-daemon
2024-07-02 9:45 ` bugzilla-daemon
2024-09-12 10:54 ` 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-209177-11613-zrh6o2oM1j@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).