Created attachment 2116264 [details] Compressed kernel messages with kernel 6.17.8-100 that had issues 1. Please describe the problem: - I have a USB video camera and I'm using zoneminder with it. When zoneminder sends the ioctl VIDIOC_S_INPUT with (at least) kernel 6.17.7-100.fc41.x86_64 and 6.17.8-100.fc41.x86_64 it's getting EBUSY. But with earlier kernels this did not happen - the last kernel I have installed is 6.16.12-100.fc41.x86_64 2. What is the Version-Release number of the kernel: 6.16.12-100.fc41.x86_64: works the same as it has the last 8+ years 6.17.7-100.fc41.x86_64: returns EBUSY 6.17.8-100.fc41.x86_64: returns EBUSY 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : I don't know all of the the kernel versions available in Fedora 41 but per above I saw this with 6.17 kernels. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Run zoneminder and it fails when sending VIDIOC_S_INPUT where that did not fail with earlier kernels. I don't have a simple test program for this. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Unknown 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Not sure where I can put it. Also here is lsusb output, the USB device with issues is the Logitech device: # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device Bus 001 Device 003: ID 2357:0604 TP-Link TP-L`nk UB500 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000 Bus 003 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub I was about to upgrade to Fedora 43 but had this problem so might wait until it has a fix - it would suck if I can't find a newer kernel that does not have this issue.
This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '41'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 41 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15. Fedora Linux 41 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.