Eric Youngdale wrote:
> Oh, duh! Now I remember why it is broken. I ran across it when I
> redid the queueing code, and it struck me that not many people could be
> using the existing code, because there was no way that it could have
> worked. I *think* I fixed the problem in the new queueing code, but we
> will find out for sure once it hits the street.
... rest omitted ...
Thank you for the easy to follow explanation about what can be
(and is) wronge about the past and interim handling of single-lun device.
> As for debugging this, I can suggest a couple of things. Start by
> examining /var/log/messages and see whether any kernel messages related to
> this device have appeared. Secondly, it would probably make better sense
> to test these things without X and just from two virtual consoles.
> Finally, I would suggest bumping up the logging levels when you run this
> test - this will make it possible to see more about what the heck the
> thing is doing. Look at the kernel configure help for
> CONFIG_SCSI_LOGGING for more information. I have some older information
> that goes into more detail on http://www.andante.org/scsi_error.html
> (the logging went in at the same time that the new error handling code
> appeared).
>
Now that the bug was more or less explained I am not sure if I need to
go in and figure out exactly whant went wrong.
But for the completeness's sake, I will try to follow the advice and
see if I can gather enough information. Maybe around Chiristmas time.
Thank you again.
Chiaki Ishikawa
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
