Jody McIntyre wrote:
can you produce a .s file following the steps in Documentation/oops-tracing.txt and try to track down exactly what is happening? If not, send me the .s and I'll see if I have time to look into it. Be sure the .s matches your configuration and patches at the time of the oops :)
Thanks for the pointer & offer. Alas I don't have a spare machine to run an alpha kernel on right now. I have to defer this.
How reproducible is this anyway?
100% with a disk which is prone to the "aborting sbp2 command" phenomenon during inquiry. Again, no other kernel ever showed this oops with any of my SBP-2 devices. Until 2.6.15-rcX, the drivers were able to recover if inquiry was aborted.
-- Stefan Richter -=====-=-=-= =-== ===-= http://arcgraph.de/sr/ - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
