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: Wed, 1 Sep 2010 05:40:52 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1009010536070.14332@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.1008310820350.19249@p34.internal.lan>
On Tue, 31 Aug 2010, Justin Piszcz wrote:
>>
Hi Adam and LSI,
LSI got back to me, they said to try their latest firwmare and that the high
I/O wait was solved in that release.
# tw_cli /c0 show all | grep -i firmware
/c0 Firmware Version = FE9X 4.10.00.016
# tw_cli /c1 show all | grep -i firmware
/c1 Firmware Version = FE9X 4.10.00.016
I upgraded to the newest firmware, 2.6.34 remains solid.
However, when I moved to 2.6.35, the high I/O weight and system freezes recur.
Has anyone not noticed this? I have two different controllers, a 4 and 16
port 9650SE, both with BBUs, one with a RAID-1 the other with a RAID-6 and
I've never had any problems like this before (this high I/O wait/ctrl reset)
until I moved to 2.6.35.
There is something wrong/happening here in 2.6.35 that causes the system
to become unresponsive and reset the controllers under high load. Prior to
2.6.35, the problem does not exist, I have confirmed this on both firmwares
now.
Could the lock/unlock be causing the issue?
Again, in 2.6.34, there are no latency problems or controller resets.
3ware diff:
--- linux-2.6.34.6/drivers/scsi/3w-9xxx.c 2010-08-26 19:44:38.000000000 -0400
+++ linux-2.6.35.4/drivers/scsi/3w-9xxx.c 2010-08-26 19:47:12.000000000 -0400
- Written By: Adam Radford <linuxraid@amcc.com>
- Modifications By: Tom Couch <linuxraid@amcc.com>
+ Written By: Adam Radford <linuxraid@lsi.com>
+ Modifications By: Tom Couch <linuxraid@lsi.com>
+ Copyright (C) 2010 LSI Corporation.
- linuxraid@amcc.com
+ linuxraid@lsi.com
- http://www.amcc.com
+ http://www.lsi.com
+ 2.26.02.014 - Force 60 second timeout default.
-#define TW_DRIVER_VERSION "2.26.02.013"
+#define TW_DRIVER_VERSION "2.26.02.014"
-MODULE_AUTHOR ("AMCC");
+MODULE_AUTHOR ("LSI");
-static int twa_chrdev_ioctl(struct inode *inode, struct file *file, unsigned int cmd, unsigned long arg);
+static long twa_chrdev_ioctl(struct file *file, unsigned int cmd, unsigned long arg);
- .ioctl = twa_chrdev_ioctl,
+ .unlocked_ioctl = twa_chrdev_ioctl,
-static int twa_chrdev_ioctl(struct inode *inode, struct file *file, unsigned int cmd, unsigned long arg)
+static long twa_chrdev_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
+ struct inode *inode = file->f_path.dentry->d_inode;
+ lock_kernel();
+
+ unlock_kernel();
+/* This function gets called when a disk is coming on-line */
+static int twa_slave_configure(struct scsi_device *sdev)
+{
+ /* Force 60 second timeout */
+ blk_queue_rq_timeout(sdev->request_queue, 60 * HZ);
+
+ return 0;
+} /* End twa_slave_configure() */
+
+ .slave_configure = twa_slave_configure,
next prev parent reply other threads:[~2010-09-01 9:41 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 [this message]
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.1009010536070.14332@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®