From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 208605] AACRAID frequent hos bus reset with intensive IO on large arrays
Date: Wed, 29 Jul 2020 07:43:18 +0000 [thread overview]
Message-ID: <bug-208605-11613-aq7JRTQLNR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208605-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208605
--- Comment #5 from Janpieter Sollie (janpieter.sollie@edpnet.be) ---
I think I found a solution:
When I force sync mode, the driver handles everything perfectly. Off course
this has a performance impact, so if anyone could help me debug this driver in
async mode, it would be very much appreciated ...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-07-29 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 6:36 [Bug 208605] New: AACRAID frequent hos bus reset with intensive IO on large arrays bugzilla-daemon
2020-07-19 7:32 ` [Bug 208605] " 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 [this message]
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-aq7JRTQLNR@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 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.