found a reason for scsi problems in 2.1.97-SMP.

Dario_Ballabio (Dario_Ballabio@milano.europe.dg.com)
Mon, 20 Apr 1998 18:09:36 +0200


I did the following modification to the EATA driver (but the same thing
is possible with almost all scsi drivers) in order to track down
the scsi problems with 2.1.97-SMP:
at the beginning of the queuecommand routine I added the test
if (SCpnt->host_scribble) panic ("SCpnt %p in use!\n", SCpnt);

SCpnt->host_scribble is set to a non zero value just before exiting
the queuecommand routine and set to zero in the interrupt routine
just before calling scsi_done.
So if SCpnt->host_scribble is non zero when queuecommand is called,
it means that it points to a scsi command which is already in use
by the low level driver.
As a matter of fact this is what happens, and this is a clear
indication of what is wrong with the upper scsi layer.
-db

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu