Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: usb-storage@lists.one-eyed-alien.net,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: Oops unplugging USB stick
Date: 13 May 2004 11:39:03 -0500	[thread overview]
Message-ID: <1084466344.2066.24.camel@mulgrave> (raw)
In-Reply-To: <200405131803.52676.oliver@neukum.org>

On Thu, 2004-05-13 at 11:03, Oliver Neukum wrote:
> May 13 16:48:20 macbeth kernel: usb 1-1: USB disconnect, address 2
> May 13 16:48:20 macbeth kernel: sd 1:0:0:0: Illegal state transition offline->cancel
> May 13 16:48:20 macbeth kernel: Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1640
> May 13 16:48:20 macbeth kernel: Call Trace:
> May 13 16:48:20 macbeth kernel:  [<c0304bda>] scsi_device_set_state+0xea/0x140
[...]

That's not actually an oops, it's just a warning that there's an error
in the state model....the machine proceeded normally after the messages
appeared, didn't it?  Actually, this one looks to be a residual of the
fix to a previous problem.  Does the attached make the message go away?

James

===== drivers/scsi/scsi_lib.c 1.126 vs edited =====
--- 1.126/drivers/scsi/scsi_lib.c	Wed Mar 31 16:32:26 2004
+++ edited/drivers/scsi/scsi_lib.c	Thu May 13 11:35:39 2004
@@ -1610,7 +1610,9 @@
 
 	case SDEV_CANCEL:
 		switch (oldstate) {
+		case SDEV_CREATED:
 		case SDEV_RUNNING:
+		case SDEV_OFFLINE:
 			break;
 		default:
 			goto illegal;
@@ -1619,9 +1621,7 @@
 
 	case SDEV_DEL:
 		switch (oldstate) {
-		case SDEV_CREATED:
 		case SDEV_CANCEL:
-		case SDEV_OFFLINE:
 			break;
 		default:
 			goto illegal;


  reply	other threads:[~2004-05-13 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 16:03 Oops unplugging USB stick Oliver Neukum
2004-05-13 16:39 ` James Bottomley [this message]
2004-05-13 17:05   ` Oliver Neukum

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=1084466344.2066.24.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=oliver@neukum.org \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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