After reviewing the dmesg files I posted, I can see a common call path to the problem: v4l2_open -> video_open -> mutex_lock The path is always related to the cx88xx drivers, for a DVB card.
Is it the DVB card drivers? To test this I added a blacklist-tmp.conf file into /etc/modprobe.d containing: > blacklist cx2341x > blacklist cx88_blackbird > blacklist cx88_dvb > blacklist cx88_vp3054_i2c > blacklist cx88_alsa > blacklist cx8802 > blacklist cx8800 > blacklist cx88xx After a reboot, the problem does not appear on any of the kernels tested. That looks like the problem is in the cx88 drivers, and how they use mutex_lock(). Looking at the kernel sources, mutex_lock() is probably a widely used piece of kernel code, and problems there would be quite widespread (I guess?...) The next step will be to look at what has changed in the cx88 drivers from 2.6.35 to 2.6.38 Regarding comment #6 I do not think it relates to this issue, but in searches I have seen other similar bugs related to the kernel scheduler. I am not sure if it was the IO or the Process scheduler. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - "blocked for more than 120 seconds" INFO message -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
