Have a Linux system with: Bus 006 Device 002: ID 0471:0311 Philips (or NXP) PCVC740K ToUcam Pro [pwc] Bus 006 Device 003: ID 0471:0311 Philips (or NXP) PCVC740K ToUcam Pro [pwc] (two identical pwc driver cams) One sits on /dev/video0 Other one sits on /dev/video1 Have /dev/video1 open by e.g. `motion`. Then, as user, open a shell, and enter: $ vlc /dev/video0 And in my case the system froze with a crashdump. (photo available)
Please attach the oops data
Created attachment 73378 [details] screenshot
Hi, Is this bug reproducable? If it is, I see in bug 4329 that you've tried switching to http://git.linuxtv.org/media_build.git does it still happen there? This may be related to the locking fix I've done recently: http://git.linuxtv.org/media_tree.git/commitdiff/ceede9fa8939e40ad0ddb4ad1355f45c6f1d3478 But TBH I don't think it is. Although I don't really have a clue if it is not that, then what has caused this backtrace... Also notice that backporting that locking fix to anything before 3.5 is non trivial as it depends on a couple of v4l2-core features which are new in 3.5. Regards, Hans
bug 4329 in my previous comments should be bug 43291 of course.
I did not test reproducibility yet. We did make progress in https://bugzilla.kernel.org/show_bug.cgi?id=43291 Tomorrow I can see if that also influences the behaviour for this bug.