Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1360688
Summary: | event decoding changed 4.4.7 -> 4.6.4 breaking user space apps. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alec Leamas <leamas.alec> | ||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 24 | CC: | gansalmon, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | kernel-4.8.0-0.rc5.git1.1.fc25 kernel-4.7.3-200.fc24 | Doc Type: | If docs needed, set a value | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2016-09-13 18:10:00 UTC | Type: | Bug | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Alec Leamas
2016-07-27 10:51:06 UTC
Created attachment 1184589 [details]
4.6.4 log
We've had breakages before (see https://bugzilla.redhat.com/show_bug.cgi?id=1260862) and they need to be reported to the upstream kernel maintainer directly. Can you run a git bisect to identify which commit specifically broke things? After some days of multitasking (bisecting & harvesting currant): first bad commit: [078600f514a12fd763ac84c86af68ef5b5267563] [media] rc-core: allow calling rc_open with device not initialized Given what (not) happened to bug #1260862, perhaps you could file the kernel bug? Obviously, not much happens when I file one :( Created attachment 1186453 [details]
Bisecty log
OK then... filed bug, see https://sourceforge.net/p/lirc/mailman/message/35267107/. Sent to maintainers as of get_maintainers.pl on the seemingly bad commit. Seems that this has been resolved upstream: http://www.spinics.net/lists/linux-media/msg103384.html. Leaving this bug open until the fix lands in fedora kernel. @laura: Any chance of adding the upstream patch to current, broken kernel? I don't see an ack from the maintainer on it. The merge window just closed a few days ago so I'd like to give it a little more time to see if anyone has any objections. If there's been no response by Friday we can bring it into Fedora. @laura: That was last Friday, time flies. Do you expect anything from me here? Can you get me the patch to bring in? If you are on the e-mail thread it would also be good to send another request for review. Created attachment 1193994 [details] rc_core: restore repeat events. Sorry, I missed your message somehow. Too much noise. Anyway, attaching a patch. I have submitted builds at copr [1], but the system seems flooded with large builds (and I add another one), so it will take some time. Perhaps some admin in some timezone can fix things. I will return once I have verified this patch, but needs clear my desk for now. I'm not on that list, and I don't have the skills to make something meaningful there, I guess. So, I havn't requested a review. Should I, given all this? [1] https://copr.fedorainfracloud.org/coprs/leamas/lirc-0.9.4-preview/ nirik into action, COPR builders OK again and indeed, the patch works fine. I'll pull the patch into branches. In the interest of encouraging upstream, start another e-mail thread on linux-media.org indicating the problem and pointing to the patch as a solution. Make sure to e-mail maintainers (Mauro Carvalho Chehab plus Hans Verkuil) along with the patch author. kernel-4.8.0-0.rc5.git1.1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-0f0a455d84 kernel-4.7.3-200.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f9d5f8f03f kernel-4.7.3-100.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-91fb402c7f kernel-4.8.0-0.rc5.git1.1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-0f0a455d84 kernel-4.7.3-100.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-91fb402c7f kernel-4.7.3-200.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f9d5f8f03f kernel-4.8.0-0.rc5.git1.1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. kernel-4.7.3-200.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. kernel-4.7.3-100.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. (In reply to Laura Abbott from comment #12) > In the interest of encouraging upstream, > start another e-mail thread on linux-media.org indicating the > problem and pointing to the patch as a solution. Make sure to e-mail > maintainers (Mauro Carvalho Chehab plus Hans Verkuil) along with the patch > author. For the record: http://www.spinics.net/lists/linux-media/msg105457.html |