public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Cornelius Claussen <cornelius.claussen@gmx.de>,
	Patrick Mansfield <patmans@us.ibm.com>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [linux-usb-devel] Problem with external USB2.0 case and LG GSA 4040-B
Date: 16 Dec 2003 13:36:00 -0500	[thread overview]
Message-ID: <1071599762.2080.116.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0312151529160.895-100000@ida.rowland.org>

I've been thinking some more about this.  Although the driver is
apparently at fault here by issuing a reset without telling the
mid-layer, it might be useful to filter out other common ASC/ASCQ codes
in scsi_io_completion() we retry on "in the process of becoming ready",
then for any other UNIT_ATTENTION, we assume it was a disc change for
removable (this is what causes the I/O error in this case) or a reset
for non-removable.

Perhaps we should do a more dilligent check for the reset case?  ASC
0x29 and ASCQ <= 4 seems to identify all the reset cases.  Since the
tape case doesn't come through here, there's no danger of doing an
incorrect retry for it.

There is, however, one danger to the removable case: a power cycle could
still be accompanied by a medium change, which would now be missed.

On the whole, I'm inclined to leave everything the way it is, but was
wondering if there were any other comments?

James



      parent reply	other threads:[~2003-12-16 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200312132137.18128.cornelius.claussen@gmx.de>
2003-12-15 20:49 ` [linux-usb-devel] Problem with external USB2.0 case and LG GSA 4040-B Alan Stern
2003-12-15 21:08   ` James Bottomley
2003-12-16 18:36   ` 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=1071599762.2080.116.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=cornelius.claussen@gmx.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=patmans@us.ibm.com \
    --cc=stern@rowland.harvard.edu \
    /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