From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Jens Axboe <axboe@suse.de>,
nickpiggin@yahoo.com.au,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Fw: oops in kernel 2.6.9
Date: 20 Oct 2004 08:32:38 -0500 [thread overview]
Message-ID: <1098279164.2002.7.camel@mulgrave> (raw)
In-Reply-To: <20041019234857.7ddf5bc7.akpm@osdl.org>
On Wed, 2004-10-20 at 01:48, Andrew Morton wrote:
> Jens Axboe <axboe@suse.de> wrote:
> >
> > On Tue, Oct 19 2004, Andrew Morton wrote:
> > >
> > > oy.
> >
> > Looks like a SCSI issue, it probably killed the queue before the io
> > scheduler was entered again.
>
> Better add linux-scsi to cc then...
The SCSI half of the fix for this is in bk latest (that was adding a
refcount to the device as soon as the command is issued). I'm not sure
about the usb-storage piece (not exciting the error handler by ignoring
commands when the device is unplugged).
James
prev parent reply other threads:[~2004-10-20 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041019175146.15889e11.akpm@osdl.org>
[not found] ` <20041020064255.GB8755@suse.de>
2004-10-20 6:48 ` Fw: oops in kernel 2.6.9 Andrew Morton
2004-10-20 13:32 ` James Bottomley [this message]
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=1098279164.2002.7.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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).