From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: Christian Vilhelm <christian.vilhelm@univ-lille2.fr>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
"James E.J. Bottomley" <James.Bottomley@suse.de>
Subject: Re: MVSAS 1669:mvs_abort_task:rc= 5
Date: Sun, 11 Oct 2009 16:58:13 -0600 [thread overview]
Message-ID: <200910111658.13639.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <4AD22532.9060001@univ-lille2.fr>
On Sun October 11 2009, Christian Vilhelm wrote:
> Thomas Fjellstrom wrote:
> > Hi,
> >
> > I've been trying to get an AOC-SASLP-MV8 card (pcie x4 2 port SAS card)
> > to work with linux for the past month or so. I've recently just RMAed my
> > first card, and tested the new one under linux, and I see the same
> > problems.
> >
> > The very first time I made a new array off the controller, formated (with
> > xfs) and mounted the volume, it seemed to work. ioozone even seemed to
> > run for a while. Sadly after a few minutes I got a stream of
> > mvs_abort_task messages in dmesg, and any accesses to the volume, or any
> > disks connected to the controller lock up.
> >
> > After that I updated my 2.6.31 kernel to 2.6.32-rc3-git2 off of
> > kernel.org, and the volume fails to mount with the same mvs_abort_task
> > messages.
>
> I have the exact same problem with another Marvell 88SE64xx based card,
> namely an Areca ARC-1300ix-16 and the mvsas driver.
> If the disks are just used alone, with a filesystem on them, all seems
> to work fine. dd and badblocks run fine on them. Mounting them,
> reading/writing work fine. The error seem to popup but rarely when
> several disks are used simultaneously.
> But, an absolute sure way to trigger the error is to assemble (or
> create) a md raid array with the disks. I join a syslog extract from the
> error. You can see it happens seconds after the array creation.
> I tried :
> 1) disabling the write cache on the disks => same error
> 2) disabling NCQ : in mv_sas.h :
> #define MV_DISABLE_NCQ 1
> same error.
> Afer a while, the devices handled by the card are just dropped from the
> system and the card stops working at all, a reboot is necessary.
I have found that a proper reboot is impossible once the card/driver starts
misbehaving. Anything that tries to do anything with the md device, or any of
the component drives will hang. Even kernel threads it seems. A reboot or a
shutdown hangs when it tries to sync the md device, and ALT+SYSRQ+S/U both
hang. After the first Alt+sysrq+s it will register more of them, but it won't
print the "Emergency Sync Complete" message.
> Does anyone have a working config based on a Marvell 64xx card ?
>
> I'm willing to explore solutions, patches or anything, just tell me what
> to do to help.
>
> Christian Vilhelm.
>
--
Thomas Fjellstrom
tfjellstrom@shaw.ca
next prev parent reply other threads:[~2009-10-11 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 17:41 MVSAS 1669:mvs_abort_task:rc= 5 Thomas Fjellstrom
2009-10-10 15:56 ` Thomas Fjellstrom
[not found] ` <20091010164422.GA8896@linux-dev>
2009-10-10 19:18 ` Thomas Fjellstrom
2009-10-11 18:34 ` Christian Vilhelm
2009-10-11 22:58 ` Thomas Fjellstrom [this message]
2009-10-14 1:39 ` Thomas Fjellstrom
[not found] ` <e938503f0910132151p20b42459v96800d889f3f63eb@mail.gmail.com>
2009-10-14 7:18 ` Thomas Fjellstrom
2009-10-14 7:55 ` Christian Vilhelm
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=200910111658.13639.tfjellstrom@shaw.ca \
--to=tfjellstrom@shaw.ca \
--cc=James.Bottomley@suse.de \
--cc=christian.vilhelm@univ-lille2.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.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 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).