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 1531927
Summary: | lirc_zilog ceased working with kernel 4.14 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Warren Sturm <warren.sturm> | ||||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | high | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 27 | CC: | airlied, bskeggs, ewk, hdegoede, hobbes1069, ichavero, itamar, jarodwilson, jcline, jglisse, john.j5live, jonathan, josef, kernel-maint, leamas.alec, linville, mchehab, mjg59, steved | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | x86_64 | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | kernel-4.16.3-200.fc27 kernel-4.16.7-100.fc26 | Doc Type: | If docs needed, set a value | ||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2018-04-27 01:20:11 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
Warren Sturm
2018-01-06 17:45:58 UTC
Hi! Thanks for reporting. That said, kernel modules is part of kernel, not lirc. Re-assigning This is still the case with 4.15.3 kernel Created attachment 1421007 [details]
dmesg output after boot with GPF OOPs
Created attachment 1421008 [details]
Error message for irsend
Created attachment 1421009 [details]
Loaded modules
Created attachment 1421010 [details]
lspci output
Created attachment 1421011 [details]
dmesg output after rmmod with another OOPs
I also tried reloading the lirc_zilog module. After a short time the system froze.
Hi, Can you test on kernel 4.16? It looks like lirc_zilog is gone in 4.16 and replaced with the ir-kbd-i2c driver. You can either install the F28 kernel[0] or use Copr to install the stablization kernel for F27[1]. Thanks! [0] https://koji.fedoraproject.org/koji/buildinfo?buildID=1069581 [1] https://copr.fedorainfracloud.org/coprs/jforbes/kernel-stabilization/ I have F28 Beta loaded on another partition and used it for testing. 4.16 requires a different lircd.conf.d entry for the ir xmit on the hvr1600 but it does work. There should be some patches available soon from the media group for 4.14 and 4.15. I did not try 4.13.16 where xmit works but rmmod OOPs as well. The OOPs goes back to 4.11 when you rmmod lirc_zilog. Cool, thanks for testing that. Since Fedora 27 will be getting the 4.16 kernel in the next week or so and I don't believe there will be any more 4.15 builds, I think the best path forward here is to mark this as fixed by the 4.16 update. Fedora 26 is at 4.15.16 I think. Here is a link for the DCT700 codes needed under 4.16 https://help.ubuntu.com/community/Motorola_DCT700_Channel_Change_Script kernel-4.16.3-200.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b6be90818d kernel-4.16.3-200.fc27 has been pushed to the Fedora 27 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-2018-b6be90818d I have tried out the 4.16.3 kernel and was able to get IR transmit working. lircd is still needed as well as the new DCT700 codes from comment 11. There will be adjustments to the lirc config files required. Thanks for testing it out. kernel-4.16.4-100.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-884a105c04 kernel-4.16.3-200.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. kernel-4.16.4-100.fc26 has been pushed to the Fedora 26 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-2018-884a105c04 kernel-4.16.5-100.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-884a105c04 kernel-4.16.6-100.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-884a105c04 kernel-4.16.6-100.fc26 has been pushed to the Fedora 26 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-2018-884a105c04 kernel-4.16.7-100.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-884a105c04 kernel-4.16.7-100.fc26 has been pushed to the Fedora 26 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-2018-884a105c04 kernel-4.16.7-100.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |