From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jens Axboe <Jens.Axboe@oracle.com>,
Mike Anderson <andmike@linux.vnet.ibm.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Block timeouts seem not to be working
Date: Thu, 11 Sep 2008 10:05:21 -0500 [thread overview]
Message-ID: <1221145521.3330.2.camel@localhost.localdomain> (raw)
I just noticed this with a rather finickey SAS system I have. It's got
a SATA DVD attached over an expander. Periodically the DVD just hangs
up, so we wait for the timeout and then send a phy reset which clears
it.
What I'm seeing with the new block timer code is that the timer never
expires. I can dig some more into this, but if you wanted to test it as
well, the timer code is easy to excite. Just throw away one command in
every 128 or so in the queuecommand routine of your favourite HBA
driver.
James
next reply other threads:[~2008-09-11 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 15:05 James Bottomley [this message]
2008-09-11 15:42 ` Block timeouts seem not to be working Mike Anderson
2008-09-11 18:35 ` Jens Axboe
2008-09-12 21:46 ` James Bottomley
2008-09-15 20:01 ` Mike Christie
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=1221145521.3330.2.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Jens.Axboe@oracle.com \
--cc=andmike@linux.vnet.ibm.com \
--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