On Sat, 2 Jan 1999, Guest section DW wrote:
>
> But this is a command to the disk that got the timeout. Strange..
> [Maybe nothing is wrong with the disk, there never is...]
Why is it attempting to reset the disk?? I am reading from the *tape drive*.
Or is target 0 the host adapter? I'm assuming target 0 is the hard disk
(SCSI ID 0).
>
> [Information as I see it: nothing is wrong with the disk.
> Nothing is wrong with the SCSI controller.
> But some error occurs somewhere, and the SCSI subsystem gets
> terminally confused.
>
> Now scsi_old_times_out() starts with spin_lock_irqsave();
> maybe handling of IRQ or io_request_lock is flawed.]
>
> If you can reproduce it, even better.
> No doubt Leonard Zubkoff will correct all that is wrong in the above.
>
> Andries
>
I have been able to reproduce this over and over. I am now going to try
2.2.0-pre3 to see if anything is different.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
