From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 207359] New: MegaRAID SAS 9361 controller hang/reset
Date: Sun, 19 Apr 2020 18:25:56 +0000 [thread overview]
Message-ID: <bug-207359-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=207359
Bug ID: 207359
Summary: MegaRAID SAS 9361 controller hang/reset
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: >=v5.4
Hardware: PPC-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-64
Assignee: platform_ppc-64@kernel-bugs.osdl.org
Reporter: cam@neo-zeon.de
Regression: No
Created attachment 288623
--> https://bugzilla.kernel.org/attachment.cgi?id=288623&action=edit
dmesg output for controller hang
On a Talos II 2x 36 core (144 thread) POWER9 box, MegaRAID SAS 9361-16i PCIE
controller can be made to pretty consistently hang with "heavy IO" on kernel
versions greater than 5.3.18.
I am unable to reproduce this on a 16/32 core/thread amd64 box with a MegaRAID
SAS 9361-16i PCIE with the exact same firmware revision.
The box also has a Microsemi SAS HBA which seems unaffected by this.
System details:
Talos II motherboard
2x 36 core (144 thread) POWER9 processors
512GB memory
4k page size
MegaRAID SAS 9361-16i PCIE controller (4 disk RAID10 volume, megaraid_sas
driver)
Microsemi HBA w/4x SSD's
The relevant dmesg messages are attached.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-04-19 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 18:25 bugzilla-daemon [this message]
2020-04-19 20:24 ` [Bug 207359] MegaRAID SAS 9361 controller hang/reset bugzilla-daemon
2020-04-19 20:55 ` bugzilla-daemon
2020-05-10 3:02 ` bugzilla-daemon
2020-08-06 17:56 ` 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-207359-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).