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
-
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/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:00:58 EST