All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Core scsi layer crashes in 2.6.8.1
Date: 29 Sep 2004 10:11:59 -0400	[thread overview]
Message-ID: <1096467125.2028.11.camel@mulgrave> (raw)
In-Reply-To: <1096401785.13936.5.camel@localhost.localdomain>

On Tue, 2004-09-28 at 16:03, Alan Cox wrote:
> Second problem is with the scsi handling logic for errors. If you rmmod
> a scsi driver while it is error handling you get a chain of errors
> starting with
> 
> 	Illegal transition Cancel->Offline
> 	Badness is scsi_device_set_state
> 	path:
> 	scsi_device_set_state
> 	scsi_unjam_host
> 	scsi_error_handler
> 

These state transition warnings are currently expected in this code
(they're basically verbose warnings).

What was the oops?

I have a theory that we should be taking a device reference before
waking up the error handler, otherwise host removal can race with error
handling.

James



  reply	other threads:[~2004-09-29 14:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 20:03 Core scsi layer crashes in 2.6.8.1 Alan Cox
2004-09-29 14:11 ` James Bottomley [this message]
2004-09-29 13:24   ` Alan Cox
2004-09-29 14:34     ` James Bottomley
2004-09-29 14:27   ` Matthew Wilcox
2004-10-05 11:49   ` Anton Blanchard
2004-10-05 13:56     ` James Bottomley
2004-10-05 14:44       ` Mark Lord
2004-10-05 14:56         ` James Bottomley
2004-10-05 15:46           ` Mark Lord
2004-10-05 15:49           ` Oliver Neukum
2004-10-05 15:54             ` James Bottomley
2004-10-05 15:57               ` Mark Lord
2004-10-05 16:01                 ` James Bottomley
2004-10-05 16:53                 ` Jeff Garzik
2004-10-05 16:01               ` Oliver Neukum
2004-10-05 16:07                 ` James Bottomley
2004-10-05 16:26                   ` Oliver Neukum
2004-10-05 16:38                     ` James Bottomley

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=1096467125.2028.11.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.