From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 60644] MPT2SAS drops all HDDs when under high I/O
Date: Mon, 13 Jan 2014 17:27:49 +0000 [thread overview]
Message-ID: <bug-60644-11613-iBsRRFvzOM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60644-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60644
--- Comment #37 from Jeff Johnson <jeff.johnson@aeoncomputing.com> ---
I can confirm Tommy's observations about disabling PERR and SERR solving the
issue.
The motherboard I am using (Supermicro X8DTH-iF) does not have those exact BIOS
settings to control. In my case the following BIOS changes and kernel command
line arguments eliminated the issue:
MB BIOS: BIOS->Advanced->Advanced Chipset Configuration->North Bridge
Configuration->ASPM=Disabled
Linux boot command line options: pcie_aspm=off disable_msi=1
With these changes a very intense fio run has gone four days without a single
error or issue on a Linux-ZFS filesystem.
Before these changes I could not go four hours without multiple HBAs
disappearing (in my config there are three HBAs). Sometimes the HBAs would
disappear within 15-20 minutes of benchmark runtime.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-01-13 17:27 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 3:20 [Bug 60644] New: MPT2SAS drops all HDDs when under high I/O bugzilla-daemon
2013-07-29 3:21 ` [Bug 60644] " bugzilla-daemon
2013-07-29 3:32 ` bugzilla-daemon
2013-07-29 11:27 ` bugzilla-daemon
2013-07-29 14:12 ` bugzilla-daemon
2013-07-29 14:14 ` bugzilla-daemon
2013-07-29 23:24 ` bugzilla-daemon
2013-07-29 23:30 ` bugzilla-daemon
2013-07-30 5:00 ` bugzilla-daemon
2013-07-30 5:26 ` bugzilla-daemon
2013-07-30 5:33 ` bugzilla-daemon
2013-07-30 10:03 ` bugzilla-daemon
2013-07-30 10:11 ` bugzilla-daemon
2013-07-30 10:12 ` bugzilla-daemon
2013-08-01 13:20 ` bugzilla-daemon
2013-08-01 14:24 ` bugzilla-daemon
2013-08-01 14:30 ` bugzilla-daemon
2013-08-02 10:44 ` bugzilla-daemon
2013-08-27 6:48 ` bugzilla-daemon
2013-08-27 7:14 ` bugzilla-daemon
2013-08-27 11:45 ` bugzilla-daemon
2013-08-27 11:46 ` bugzilla-daemon
2013-08-27 15:29 ` bugzilla-daemon
2013-08-28 7:57 ` bugzilla-daemon
2013-08-28 8:32 ` bugzilla-daemon
2013-08-28 8:44 ` bugzilla-daemon
2013-08-28 13:33 ` bugzilla-daemon
2013-08-29 5:51 ` bugzilla-daemon
2013-08-29 10:09 ` bugzilla-daemon
2013-08-29 19:34 ` bugzilla-daemon
2013-08-30 3:08 ` bugzilla-daemon
2013-08-30 4:56 ` bugzilla-daemon
2013-09-17 11:00 ` bugzilla-daemon
2013-09-20 10:13 ` Pasi Kärkkäinen
2013-09-20 10:28 ` bugzilla-daemon
2013-09-20 14:38 ` bugzilla-daemon
2013-12-05 18:00 ` bugzilla-daemon
2014-01-02 14:40 ` bugzilla-daemon
2014-01-13 17:27 ` bugzilla-daemon [this message]
2014-01-13 17:31 ` bugzilla-daemon
2014-01-13 18:02 ` bugzilla-daemon
2014-01-13 19:41 ` bugzilla-daemon
2014-01-19 12:14 ` bugzilla-daemon
2014-01-19 12:15 ` bugzilla-daemon
2014-01-19 12:17 ` bugzilla-daemon
2014-01-20 18:27 ` bugzilla-daemon
2014-01-20 18:39 ` bugzilla-daemon
2014-01-20 18:42 ` bugzilla-daemon
2014-01-21 2:54 ` bugzilla-daemon
2014-01-21 19:46 ` bugzilla-daemon
2016-03-29 15:02 ` bugzilla-daemon
2016-12-28 11:15 ` bugzilla-daemon
2016-12-28 11:18 ` bugzilla-daemon
2017-02-19 11:55 ` 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-60644-11613-iBsRRFvzOM@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.