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: Mon, 09 Oct 2023 08:29:50 +0000 [thread overview]
Message-ID: <bug-209177-11613-jTVcQ3wgIO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209177-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209177
Lynn Davenport (growthstarboard@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |growthstarboard@gmail.com
--- Comment #7 from Lynn Davenport (growthstarboard@gmail.com) ---
(In reply to Akemi Yagi from comment #5)
> This bug has been reported for Fedora (kernel 5.8.6):
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1878332
> https://penaltykickonline.com
I can attest that the value "mpt3sas.max_queue_depth=10000" was effective
there, despite a few peculiar and maybe cosmetic issues that I'll transcribe
once I have them in text form.
--
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:[~2023-10-09 8:29 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 [this message]
2024-06-22 11:32 ` bugzilla-daemon
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-jTVcQ3wgIO@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).