From: Benjamin Schindler <bschindler@inf.ethz.ch>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, support@areca.com.tw
Subject: Re: arcmsr serious issues
Date: Fri, 05 Jun 2009 20:20:44 +0000 [thread overview]
Message-ID: <4A297E1C.90704@inf.ethz.ch> (raw)
In-Reply-To: <alpine.LNX.2.01.0906051003270.18210@filesrv1.baby-dragons.com>
Hi
I used the gentoo-livecd and an installed system (Which I sent the
.config with)
Both kernels exhibit the very same problem. I'm sorry that the two don't
mix.
I have dmesg which shows similar behaviour. However, that machine just
died (Power supply broken - it will take some time until I get it back)
so I cannot post that data now.
Cheers
Benjamin
Mr. James W. Laferriere wrote:
> On Fri, 5 Jun 2009, James Bottomley wrote:
>> On Fri, 2009-06-05 at 16:19 +0200, Benjamin Schindler wrote:
>>> Hi
>>> (I'm not subscribed to this list, so please cc me)
>>>
>>> I tried to install gentoo linux on a areca ARC-1210 raid controller,
>>> but
>>> I'm having serious issues. The problem start on more heavy I/O with:
>>>
>>> arcmsr6: abort device command of scsi id = 0 lun = 0
>>>
>>> From this point, the system has serious issues. With xfs for example,
>>> the following happens:
>>>
>>> arcmsr6: abort device command of scsi id = 0 lun = 0
>>
>> This is an abort, likely triggered by a timeout.
>>
>>> sd 6:0:0:0: [sda] Result: hostbyte=DID_OK
>>> driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
>>
>> This looks very suggestive, nothing in the arcmsr ... or indeed any
>> driver ever sets DRIVER_TIMEOUT ... it looks like a mangled result code
>> somehow. It definitely lead to the resulting failure.
>>
>> Cc:ing Areca people to see if they have any idea.
>>
>> James
>
> I am QUITE sure the .config as shown did not create the kernel
> messages as shown . One does have to enable the 'CONFIG_FUSION' in
> order to use it .
>
> ... Snipped to show context .
>
>>> Fusion MPT base driver 3.04.07
>
> ... Snipped to show context .
>
>>> Copyright (c) 1999-2008 LSI Corporation
>>> sda1 sda2
>>> sd 6:0:0:0: [sda] Attached SCSI disk
>>> sd 6:0:0:0: Attached scsi generic sg1 type 0
>>> scsi 6:0:16:0: Attached scsi generic sg2 type 3
>>> Fusion MPT SPI Host driver 3.04.07
>>> Fusion MPT FC Host driver 3.04.07
>>> Fusion MPT SAS Host driver 3.04.07
>
> ... Snipped to show context .
>
>>> # CONFIG_FUSION is not set
>
> ... Snipped to show context .
>
> Hth , JimL
next prev parent reply other threads:[~2009-06-05 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 14:19 arcmsr serious issues Benjamin Schindler
2009-06-05 14:30 ` James Bottomley
2009-06-05 18:07 ` Mr. James W. Laferriere
2009-06-05 20:20 ` Benjamin Schindler [this message]
2009-06-05 20:22 ` Benjamin Schindler
2009-06-08 7:14 ` Benjamin Schindler
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=4A297E1C.90704@inf.ethz.ch \
--to=bschindler@inf.ethz.ch \
--cc=James.Bottomley@HansenPartnership.com \
--cc=babydr@baby-dragons.com \
--cc=linux-scsi@vger.kernel.org \
--cc=support@areca.com.tw \
/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