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: Fri, 27 Aug 2010 13:10:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1008271306100.24692@p34.internal.lan> (raw)
In-Reply-To: <AANLkTik0BSJC5DJtVNw-MA9cuoAEUrw-M1Dn4XaF99u4@mail.gmail.com>
On Fri, 27 Aug 2010, adam radford wrote:
> Justin,
>
> This just means the firmware didn't complete an ioctl in 60 seconds.
>
> Can try changing this define in 3w-9xxx.h:
>
> #define TW_IOCTL_CHRDEV_TIMEOUT 60 /* 60 seconds */
>
> to 90 or 120 seconds to see if that fixes your issue?
>
> Thanks,
>
> -Adam
>
Hi Adam,
Thanks for responding!
LSI just got back to me on a second case, their latest beta firmware:
http://www.lsi.com/DistributionSystem/AssetDocument/readme.txt
SCR 2196: Unexpected controller soft resets
Fixed an issue with regards to deferral of write and read commands to
help eliminate unexpected soft resets.
Well well!
Plan of action:
1. See if the error recurs without 'nobarrier' - only because there are
some threads about problems when this is enabled on 3ware controllers.
2. LSI recommended I disconnect/replace my BBU module, I already did once
before, ~$120, so the next step I will apply their latest Beta firmware.
3. If it STILL does it, I can increase the timeout, HOWEVER, when I see
this, I/O on the system, everything locks up for 60-120-180-360 seconds
and then it comes back after it resets the controller. The weird thing is
this controller is only for a /data volume and not the root filesystem.
The root filesystem is on a separate RAID-1 4 port card (also w/BBU).
If you google that exact error, there is very little information, if I
find something that works, I'll update the list so others have something
to point to when they see this problem.
Justin.
next prev parent reply other threads:[~2010-08-27 17:10 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 [this message]
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
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.1008271306100.24692@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®