On Mon, Nov 28, 2005 at 08:56:54PM +0100, Stefan Richter wrote: > I am quite certain that when I first saw the oops I had all post-2.6.14 > ieee1394 updates applied, i.e. the sbp2_command_orb_lock fix too. It > happened the same way with and without these ieee1394 updates. Darn. Well, 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 :) How reproducible is this anyway? Cheers, Jody > -- > Stefan Richter > -=====-=-=-= =-== ===-- > http://arcgraph.de/sr/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > mailing list linux1394-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/linux1394-devel -- - : 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
