From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jens Axboe <axboe@suse.de>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Pedro Larroy <piotr@larroy.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [BUG] 2.6.9-rc2 scsi and elevator oops when I/O error
Date: 11 Oct 2004 09:03:31 -0500 [thread overview]
Message-ID: <1097503418.2031.14.camel@mulgrave> (raw)
In-Reply-To: <20041011095035.GE2290@suse.de>
On Mon, 2004-10-11 at 04:50, Jens Axboe wrote:
> It's not, it clearly looks like SCSI trying to kill off the queue
> with pending commands.
That's what it looks like to me too ... there should be a fix for this
in the scsi-misc-2.6 tree.
James
next prev parent reply other threads:[~2004-10-11 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 5:03 [BUG] 2.6.9-rc2 scsi and elevator oops when I/O error Pedro Larroy
2004-10-11 8:10 ` Nick Piggin
2004-10-11 9:50 ` Jens Axboe
2004-10-11 14:03 ` James Bottomley [this message]
2004-10-11 19:07 ` [linux-usb-devel] " Alan Stern
2004-10-11 15:12 ` Pedro Larroy
2004-10-11 15:24 ` Pedro Larroy
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=1097503418.2031.14.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=nickpiggin@yahoo.com.au \
--cc=piotr@larroy.com \
/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;
as well as URLs for NNTP newsgroup(s).