From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: adam radford <aradford@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: 3w-9xxx: scsi0: WARNING: (0x06:0x0037): Character ioctl (0x108) timed out, resetting card.
Date: Thu, 2 Sep 2010 18:19:49 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1009021818040.3149@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.1009021025190.16817@p34.internal.lan>
On Thu, 2 Sep 2010, Justin Piszcz wrote:
>
>
> On Thu, 2 Sep 2010, Justin Piszcz wrote:
>
>>
>>
>> On Wed, 1 Sep 2010, adam radford wrote:
>>
>>> On Wed, Sep 1, 2010 at 2:40 AM, Justin Piszcz <jpiszcz@lucidpixels.com>
>>> wrote:
>>>
>>>> Could the lock/unlock be causing the issue?
>>>> Again, in 2.6.34, there are no latency problems or controller resets.
>>>
>>> Justin,
>>>
>>> We are looking into this issue and should get back to you soon.
>>>
>>> The lock/unlock() kernel calls were not added by me but were part of a
>>> series of 'BKL pushdown' patches added by someone to all drivers with
>>> an ioctl interface. If you think those might be related to your
>>> issue, you could try
>>> removing those 2 lines of code and recompiling.
>>>
>>> If you haven't already, please email you kernel .config files for both
>>> the working kernel and non working kernel to the 3ware/LSI support
>>> people you are in contact with.
>>>
>>> Thanks.
>>>
>>> -Adam
>>>
>>
>
> I spoke too fast, it also happens with the 2.6.34 driver under 2.6.35.
> I will have to research this more, until then I'll stick with 2.6.34.
>
> Justin.
>
>
Adam/all,
Any recommendations on how to capture the freezing between the two kernels?
Which debug method would be best?
Does anyone else experience high wait times under 2.6.35 that uses 3ware cards?
I tested under another host with 2.6.35 (software raid only) and it did not
have any issues..
Justin.
next prev parent reply other threads:[~2010-09-02 22:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 13:12 Justin Piszcz
2010-08-27 16:29 ` adam radford
2010-08-27 17:10 ` Justin Piszcz
2010-08-29 15:49 ` Justin Piszcz
2010-08-31 11:21 ` Justin Piszcz
2010-08-31 11:36 ` Justin Piszcz
2010-08-31 12:23 ` Justin Piszcz
2010-08-31 18:15 ` adam radford
2010-09-01 9:40 ` Justin Piszcz
2010-09-02 0:25 ` adam radford
2010-09-02 14:21 ` Justin Piszcz
2010-09-02 14:29 ` Justin Piszcz
2010-09-02 22:19 ` Justin Piszcz [this message]
2010-09-02 23:34 ` adam radford
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=alpine.DEB.2.00.1009021818040.3149@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=aradford@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®