Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S263135AbSJVQJC>; Tue, 22 Oct 2002 12:09:02 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S263366AbSJVQJC>; Tue, 22 Oct 2002 12:09:02 -0400
Received: from mimas.island.net ([199.60.19.4]:6156 "EHLO mimas.island.net")
	by vger.kernel.org with ESMTP id <S263135AbSJVQI7>;
	Tue, 22 Oct 2002 12:08:59 -0400
Date: Tue, 22 Oct 2002 09:14:55 -0700 (PDT)
From: andy barlak <andyb@island.net>
Reply-To: <andyb@island.net>
To: Patrick Mansfield <patmans@us.ibm.com>
cc: Mike Anderson <andmike@us.ibm.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi_error device offline fix
In-Reply-To: <20021022083815.A61@eng2.beaverton.ibm.com>
Message-ID: <Pine.LNX.4.30.0210220905560.20878-100000@tosko.alm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2375
Lines: 74


On Tue, 22 Oct 2002, Patrick Mansfield wrote:
> Try removing the scsi_load_identifier call in scsi_scan.c and
> see if you can boot. And/or get sg_utils and on your 2.4 system
> send a INQUIRY page 0 to the device, and see if that hangs or
> not, like:


On this 2.4.19 box with the Buslogic 958, that command hangs:
# ./sg_inq -e -o=0 /dev/sg1
EVPD INQUIRY, page code=0x00:

Dmesg reports a growing list of:
.
.
.
SCSI host 0 abort (pid 41290) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi0: Resetting BusLogic BT-958 due to Target 1
scsi0: *** BusLogic BT-958 Initialized Successfully ***
SCSI host 0 abort (pid 41292) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi0: Resetting BusLogic BT-958 due to Target 1
scsi0: *** BusLogic BT-958 Initialized Successfully ***
.
.
.


> On Mon, Oct 21, 2002 at 05:58:04PM -0700, andy barlak wrote:
> > On Mon, 21 Oct 2002, Patrick Mansfield wrote:
> > > Can you turn on all scsi logging - with CONFIG_SCSI_LOGGING enabled,
> > > on your boot command line add a "scsi_logging=1" and send
> > > the output.
> > >
> > > -- Patrick Mansfield
> >
> > Sure.  large dmesg buffer required.  This produced a 55k file that
> > I will pare down to what I consider informative.
>
> It looks like the INQUIRY page code 0 is timing out and appears to have
> hung the bus, as all other commands sent to the bus then timeout.
>
> It's surprising that that would hang the bus.
>
> That driver really needs at least some basic reset handling.
>
> Try removing the scsi_load_identifier call in scsi_scan.c and
> see if you can boot. And/or get sg_utils and on your 2.4 system
> send a INQUIRY page 0 to the device, and see if that hangs or
> not, like:
>
> [patman@elm3a50 sg_utils]$ sudo ./sg_inq  -e -o=0 /dev/sg1
> EVPD INQUIRY, page code=0x00:
>  Only hex output supported
>  00     00 00 00 0c 00 03 80 81  c0 c1 c2 c3 c7 c8 d1 d2    ................
>
> FYI sg_utils is at:
>
> http://www.torque.net/sg/index.html#Utilities:%20sg_utils%20and%20sg3_utils
> http://www.torque.net/sg/p/sg3_utils-1.01.tgz
>
> -- Patrick Mansfield
>

-- 

 Andy Barlak

-
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/