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: Tue, 31 Aug 2010 07:36:46 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1008310732120.5156@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.1008310717260.4858@p34.internal.lan>
On Tue, 31 Aug 2010, Justin Piszcz wrote:
>
>
> On Sun, 29 Aug 2010, Justin Piszcz wrote:
>
>> On Fri, 27 Aug 2010, Justin Piszcz wrote:
Per my earlier message, both cards were resetting, scsi0 and scsi1 under
kernel 2.6.35(.x), with 2.6.34, the lag problem is gone and my machine is
back to normal again. It is unlikely that both cards would be at fault,
in addition I spent several hours trying different things, removing the BBU
modules for example, but always staying on the 2.6.35 kernel.
I am now able to run rss2email (which ALWAYS caused the machine to lockup
and freeze until one of the controllers reset) without any problems using
2.6.34.
2.6.34.1 = good
2.6.35.x = has 3ware bug
There appears to be a bug in the commit for the 3w-9xxx updates.
On 2.6.34 now and no problems so far, I am continuing to test.
http://marc.info/?l=linux-kernel&m=127419418304483&w=2
Adam Radford (2):
3ware maintainers update
3w-xxxx, 3w-9xxx: force 60 second timeout
Justin.
next prev parent reply other threads:[~2010-08-31 11:36 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 [this message]
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
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.1008310732120.5156@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®