-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
akvcam is just unstable #25
Comments
Just installed the non-lowlatency kernel and retested.. no change (never had any issues with low-latency kernel -- the RT patches from Ingo Molnar back in the 2.6 kernel days could cause issues with certain video cards, but that was so 10+ years ago). Not sure what happened, but akvcam used to be able to be rmmod / insmod (modprobed) no problem. Perhaps I need to roll back to older akvcam code/commit? |
Try insmoding with loglevel=7 and check with dmesg if it gives more information. |
I fully confirm everything this. I have exactly the same problem. |
Fresh boot and now some unknown symbol issue:
P.S.> upgraded from -51 to -53 .. was running 5.3.0-51-lowlatency before.. I can try on 5.6 but don't expect things to get better. |
@dx9s you upgraded or changed to a different kernel version, you must
|
I actually did that and more.. Just updated with another kernel update.. will try again (perhaps this was a known issue in kernel release). |
Updated to the current HWE release (5.3.0.53.110) .. think it was .109 before but wasn't paying attention / HWE are a bit more leading edge. I actually re-checked out the latest master and did a make clean (was on an Apr 7 commit prior, to getting the Apr 12 commit above. made a clean / make all and built test against several different kernels as outlined originally. -- okay machine locked up but lucky firefox saved what I had in this dialog box. Able to install the kernel module once and run cheese once and point at the vcam .. it locked up the second time I loaded cheese and had to hold power button down. Cannot tell you what was inside dmesg as the machine hard locked up again. --Doug |
I pulled the logs from kern.log and it's huge for the parts dealing with akvcam .. not sure where to post it |
Figure shoving a HUGE log file into an open issue: webcamoid#25 Isn't a nice thing to do!
forked / create a logs branch and shoved a file in over on my fork here: https://github.com/dx9s/akvcam/blob/logs/logs/dx9s-2020-05-24-kern.log https://github.com/dx9s/akvcam/blob/logs/logs/dx9s-2020-05-26-kern.log [Edit: Added/separated 24th and 26th logs] |
Looks like it locked up because it possibly dropped connection to my USB keyboard/mouse during the kernel oops (page fault in the akvcam kernel module). Page faults are not good! |
switched to older kernel and tried again, was able to reboot machine, but it was not happy during shutdown: https://github.com/dx9s/akvcam/blob/logs/logs/dx9s-2020-05-26-%232.log NOTE there might also be a conflict between /dev/video? .. in the dmesg output you can clearly see /dev/video1 reference: This is weird because I have an ACTUAL hardware capture device that is using /dev/video0 AND /dev/video1 (the way that the kernel provides two DEVs for a single v4l2 device these days) --Doug |
And now what i can do? |
Test latest commit. |
This bug may be fixed in 1.1.0, closing. |
[fwiw: at * commit 5f94c37 (HEAD -> master, tag: 1.0.4, origin/master, origin/HEAD)]
At first I thought it was an issue with more than one connection, but a single has same issues:
It has been difficult to document what I have so far, because after akvcam stops responding to "capture" programs (in this case cheese for reference), the system is unstable in various ways. Reboots usually lock up, removing the driver fails (it's "busy") so can't reload. Often before a reboot, the system usually stops responding in some fashion (keyboard, mouse, screen lockups].
I've tried older kernels (4.15, 4.18, currently on latest hwe 5.3 / all lowlatency).
At this point not sure what to do -- will continue to poke at it and try to make it usable.
config.ini:
then simple run cheese at it twice.. Second time Cheese complains about the device not working:
[...]
The text was updated successfully, but these errors were encountered: