New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading the kernel module floods journalctl with call traces #257
Comments
which exact version of |
It should still be the latest on master, e1ca7ad I don't even use the releases these days since they seem to come too late for everything to stay in working shape sometimes. |
Just a regular |
Same issue here. You can trigger it just by adding the exclusive_caps option. v4l_querycap() WARNs you if the driver change the device_caps. Maybe the issue could be solved without WARN but I do not know how. I am not deep into the v4l thing. Read v4l_querycap() line 1074: |
Maybe the exclusive_caps (V4L2_CAP_VIDEO_CAPTURE/V4L2_CAP_VIDEO_OUTPUT) should be set earlier in init_vdev(), so then there should be no warn again because the v4l_querycap() assertion should not hit. The information is then already in the file descriptor read out here: |
Can replicate (current master, i.e. v0.12.4, on Linux 5.5.15-200.fc31.x86_64 SMP) with just |
These are the commands I do to get this to happen:
Then
journalctl -b
first shows the list of kernel modules and something like these lines twice:After that, it starts repeating these lines around four times a second:
System information:
The text was updated successfully, but these errors were encountered: