From: "Kristleifur Daðason" <kristleifur@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: 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: Fri, 4 Dec 2009 19:08:49 +0000 [thread overview]
Message-ID: <73e903670912041108o32c28af3q5a61e5a2e33edd0a@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0912041952370.23464@uplift.swm.pp.se>
On Fri, Dec 4, 2009 at 7:00 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Thu, 3 Dec 2009, Kristleifur Dađason wrote:
>
>> On Thu, Dec 3, 2009 at 9:17 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>>>
>>> On Wed, 4 Nov 2009, Andre Tomt wrote:
>>>
>>>> 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).
>>>
>>> Would just like to chime in with a "me too" on this. I've tried both ubuntu
>>> 9.10 kernel (2.6.31) and their 10.04 pre-alpha (guess it's 2.6.32-rc8) and
>>> mvsas + AOC-SASLP-MV8 is pretty much unusable. If I start md creation it
>>> stalls immediately and gets nowhere, last time I tried it md claimed it had
>>> written 160 blocks then it stalled (all drive LEDs on the controller is
>>> constantly lit).
>>>
>>> If I boot without drives and then hot-plug the drives, it immediately
>>> oops:es.
>>>
>>> Any code/fixes I can try, this is a lab machine so I can easily do whatever
>>> needed with it...
>>>
>>
>> Hi,
>>
>> I had a bit of trouble finding some patches that were released by Andy Yan at
>> Marvell on November 9th, so here is a link:
>>
>> 1/7: http://kerneltrap.org/mailarchive/linux-scsi/2009/11/9/6558753
>
> They applied cleanly to the ubuntu 10.04 2.6.32 kernel source package but when compiling I received an error about "sas_change_queue_depth" having wrong amount of arguments:
>
> - sas_change_queue_depth(sdev, MVS_QUEUE_SIZE);
> + sas_change_queue_depth(sdev, MVS_QUEUE_SIZE, SCSI_QDEPTH_DEFAULT);
>
> So I removed that change and then things compiled, booted properly, but just froze when I plugged in the disks (including some garbled graphics on my X screen). That patch set doesn't seem to be ok.
(This is resent as my first email was HTML formatted and rejected by
the list. Edited and amended also.)
Cheers for trying them out! For the record, I think they were made
against 2.6.31, perhaps the original 2.6.31 rather than later 2.6.31.x
releases.
And also, I recommend using the mainline kernel for Ubuntu, especially
when trying these patches. It's available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/ - including source
packages.
-- Kristleifur
next prev parent reply other threads:[~2009-12-04 19:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 10:14 2.6.31-rc8 libata WARNING? Thomas Fjellstrom
2009-09-09 16:30 ` 2.6.31-rc9 kernel BUG (was: Re: 2.6.31-rc8 libata WARNING?) Thomas Fjellstrom
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:56 ` Thomas Fjellstrom
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 ` 2.6.31-rc9 kernel BUG and mvsas Andre Tomt
2009-11-04 1:05 ` 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 [this message]
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=73e903670912041108o32c28af3q5a61e5a2e33edd0a@mail.gmail.com \
--to=kristleifur@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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
all inboxes | Powered by JetHome®