From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 89531] New: mpt2sas: only every second disk working with PCIe x4 connection
Date: Wed, 10 Dec 2014 18:36:38 +0000 [thread overview]
Message-ID: <bug-89531-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=89531
Bug ID: 89531
Summary: mpt2sas: only every second disk working with PCIe x4
connection
Product: SCSI Drivers
Version: 2.5
Kernel Version: 3.16.5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: Other
Assignee: scsi_drivers-other@kernel-bugs.osdl.org
Reporter: abusse@cs.tu-berlin.de
Regression: No
Created attachment 160351
--> https://bugzilla.kernel.org/attachment.cgi?id=160351&action=edit
syslog
I have an SAS controller with LSI SAS 2008 controller in a PCIe slot with only
four lanes where the card can use up to eight lanes. I have the following
issue. Lets assume there are four drives attached to the controller
(sda...sdd). I use the following simple benchmark "cat /dev/sdX | pipebench >
/dev/null". When accessing every drive individually, every thing works fine.
However when I run the experiment on sda and sdb concurrently, it still works
on sda but the benchmarks stalls on sdb. When I kill the benchmark after some
seconds I see the error messages in the attachment.
However, it gets more strange. When I run the benchmark concurrently on sda and
sdc every thing works as expected. When trying to read sdb or sdd concurrently
it always results in the error described above.
I also tried to change the hardware setup and only used every second connection
of the card. However the result stayed the same: concurrent access to every
second disk fails.
In the same machine I have the same SAS controller model in a PCIe x16 slot and
there every thing works like a charm. I also swaped the cards and the issue
stays with the PCIe x4 slot. So a defective card as the source of the problem
can be ruled out.
Thank you
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2014-12-10 18:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-89531-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 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.