All of lore.kernel.org
 help / color / mirror / Atom feed
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:32:44 +0000	[thread overview]
Message-ID: <bug-209177-11613-PllCSwWIIw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209177-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209177

Guido Serra (zeph@fsfe.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zeph@fsfe.org

--- Comment #8 from Guido Serra (zeph@fsfe.org) ---
Hi, I'm having probably a related issue to this one on 6.1.0-21-amd64
Debian/bookwork (plain new installation). I cannot see any of the devices
attached to this card, lsscsi returns only the devices attached to the
motherboard

23:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express
Fusion-MPT SAS-2 [Falcon] (rev 03)
        Subsystem: Broadcom / LSI 9210-8i
        Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 25
        I/O ports at e000 [size=256]
        Memory at e2540000 (64-bit, non-prefetchable) [size=16K]
        Memory at e2100000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at <ignored> [disabled]
        Capabilities: [50] Power Management version 3
        Capabilities: [68] Express Endpoint, MSI 00
        Capabilities: [d0] Vital Product Data
        Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [c0] MSI-X: Enable+ Count=15 Masked-
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [138] Power Budgeting <?>
        Capabilities: [150] Single Root I/O Virtualization (SR-IOV)
        Capabilities: [190] Alternative Routing-ID Interpretation (ARI)
        Kernel driver in use: mpt3sas
        Kernel modules: mpt3sas

I attempted, as reported on several forums, to alter
`mpt3sas.max_queue_depth=10000` as the Queue detected was pretty low

   mpt2sas_cm0: Current Controller Queue Depth(3364),Max Controller Queue
Depth(3432)

The change seem to have absolutely no effect... shall I open a new bug? Want me
to create a bug at Debian first? how can I proceed here? I initially opened one
here as the initial installation was a Mint, and the ticket was closed abruptly
https://github.com/linuxmint/cinnamon/issues/12251

-- 
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.

  parent reply	other threads:[~2024-06-22 11:32 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 [this message]
2024-06-22 11:49 ` bugzilla-daemon
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-PllCSwWIIw@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 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.