From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 208605] New: AACRAID frequent hos bus reset with intensive IO on large arrays
Date: Sun, 19 Jul 2020 06:36:30 +0000 [thread overview]
Message-ID: <bug-208605-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=208605
Bug ID: 208605
Summary: AACRAID frequent hos bus reset with intensive IO on
large arrays
Product: SCSI Drivers
Version: 2.5
Kernel Version: 4.14 - 5.7.8
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: AACRAID
Assignee: scsi_drivers-aacraid@kernel-bugs.osdl.org
Reporter: janpieter.sollie@edpnet.be
Regression: No
Created attachment 290345
--> https://bugzilla.kernel.org/attachment.cgi?id=290345&action=edit
quick and dirty patch to fix the issue
On a large array (>15 drives), it is impossible to backup the storage to a SAS
tape without the driver detecting a lockup, and causing a bus reset.
This seems to be a false detection, as the host controller actually is not
locking up anything. It's just a bit delayed.
This issue seems to go back to 4.14.
I reverted some cleanup stuff introduced in 4.14, and the driver is working
correctly.
I attached a patch for it, but this is just to show where the bug may be, it is
not ready for production (though it works, but this may be for 7 series only).
I also have no idea what exactly causes this issue
Bug observed on a series 7 controller with a 12-drive RAID6 array.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-07-19 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 6:36 bugzilla-daemon [this message]
2020-07-19 7:32 ` [Bug 208605] AACRAID frequent hos bus reset with intensive IO on large arrays bugzilla-daemon
2020-07-19 10:08 ` bugzilla-daemon
2020-07-19 12:31 ` bugzilla-daemon
2020-07-20 10:22 ` bugzilla-daemon
2020-07-29 7:43 ` bugzilla-daemon
2020-08-12 9:10 ` 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-208605-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).