I'm writing a camera driver (qc-usb), and maybe it's buggy, but has anyone experienced a kernel crashes like the following:
When using two USB cameras simultaneously in different USB busses (a single bus has no enough bandwidth for two cameras) and then killing the two viewers simultaneously (e.g. killall -9 xawtv) there's maybe 1/3 chance for total immediate kernel crash/hang. Usually everything just stops, no oops nor panic messages, and even Sysrq keys don't work. However, rarely I get forever loop of messages on text console that suggest that do_IRQ is called recursively and stack runs out. (I wrote the messages on paper but don't have it right here). Otherwise system is similarly locked up (no Sysrq). Nothing similar happens with 2.4.x with the same driver; also on another computer (even with SMP) with just single USB bus (when the simultaneously running cameras work by turns) I have been unable to reproduce the problem. Has anyone any clue why this could happen? How to start debugging it? Has/could someone try the same thing with some other camera driver? The computer in question is single AMD Athlon 2079.556 MHz, 512 MB memory. Kernel 2.6.0 with all debugging turned on. NForce motherboard with USB 2.0 and ehci and ohci drivers loaded. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
