From: Andre Tomt <andre@tomt.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: tfjellstrom@shaw.ca, linux-kernel@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: 2.6.31-rc9 kernel BUG and mvsas
Date: Wed, 04 Nov 2009 01:50:41 +0100 [thread overview]
Message-ID: <4AF0CFE1.8050407@tomt.net> (raw)
In-Reply-To: <4AA7F965.6020408@garzik.org>
Jeff Garzik wrote:
> On 09/09/2009 12:30 PM, Thomas Fjellstrom wrote:
>> No errors on that disk. Other than the one above, and its more of a
>> warning.
>> However, I just rebooted to add some extra drives, thinking everything
>> was
>> working a little better now that I've updated to 2.6.31-rc9, I'm
>> treated to
>> the following two messages right after boot (and a system lockup to
>> boot):
Jeff & Co,
Just chiming in with a "me too" comment.
Identical issues with the AOC-SASLP-MV8 card with 8 Seagate Barracuda
7200.11 1.5TB drives using the mvsas driver. Creating a md raid array
seems to trigger it nearly instantly, however other loads do not trigger
it as fast (if at all, only tested briefly with paralell dd).
Not sure if its related in any way, but I also noticed that with
parallell dd read on all ports, the card/driver tops out at 600MB/s even
though the card is in a northbridge connected slot running in x4 mode.
Only the first 4-5 ports run at nearly full speed, while the rest barely
gets to read any data at all. To illustrate, it looks sort of like this
in iostat -m:
sda 122
sdb 122
sbc 120
sdd 121
sde 100
sdf 10
sdg 5
sdh 5
Starting to think this driver has some issues with concurrency.. The
other controllers have no issues saturating all their ports, even if
they are on a south bridge connected slot.
Same disks/setup works just fine on AHCI and sata_mv controllers on the
same computer, easily pushes 8-900MB/s with md software raid5/6 (Yipes!)
next prev parent reply other threads:[~2009-11-04 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909090414.41274.tfjellstrom@shaw.ca>
[not found] ` <200909091030.13147.tfjellstrom@shaw.ca>
2009-09-09 18:52 ` 2.6.31-rc9 kernel BUG and mvsas Jeff Garzik
2009-09-09 19:10 ` Thomas Fjellstrom
2009-09-09 20:07 ` Thomas Fjellstrom
2009-09-10 23:55 ` Thomas Fjellstrom
2009-09-11 16:04 ` Thomas Fjellstrom
2009-09-13 0:43 ` Jeff Garzik
2009-09-13 4:59 ` Thomas Fjellstrom
[not found] ` <200909122256.50474.tfjellstrom@shaw.ca>
2009-09-15 16:20 ` Thomas Fjellstrom
2009-09-17 15:39 ` 2.6.31-git4 mvsas DRIVER_TIMEOUT Thomas Fjellstrom
2009-11-04 0:50 ` Andre Tomt [this message]
2009-11-04 1:05 ` 2.6.31-rc9 kernel BUG and mvsas Andre Tomt
2009-12-03 21:17 ` Mikael Abrahamsson
2009-12-03 21:36 ` Kristleifur Daðason
2009-12-04 19:00 ` Mikael Abrahamsson
2009-12-04 19:08 ` Kristleifur Daðason
2009-12-05 10:54 ` Mikael Abrahamsson
2009-12-10 19:25 ` Mikael Abrahamsson
2009-12-10 21:04 ` Thomas Fjellstrom
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=4AF0CFE1.8050407@tomt.net \
--to=andre@tomt.net \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tfjellstrom@shaw.ca \
/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).