Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268482AbUI2OPB (ORCPT ); Wed, 29 Sep 2004 10:15:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268457AbUI2OMx (ORCPT ); Wed, 29 Sep 2004 10:12:53 -0400 Received: from stat16.steeleye.com ([209.192.50.48]:27338 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S268447AbUI2OMH (ORCPT ); Wed, 29 Sep 2004 10:12:07 -0400 Subject: Re: Core scsi layer crashes in 2.6.8.1 From: James Bottomley To: Alan Cox Cc: Linux Kernel Mailing List , SCSI Mailing List In-Reply-To: <1096401785.13936.5.camel@localhost.localdomain> References: <1096401785.13936.5.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-9) Date: 29 Sep 2004 10:11:59 -0400 Message-Id: <1096467125.2028.11.camel@mulgrave> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 889 Lines: 30 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/