Description of problem:
Recent update to kernel 4.12.9 halted the Function keys on some laptop (in this case, ASUS X550ZE). Previous version 4.11.x has hotkeys working as intended.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Update to the latest stable kernel
Function keys (multimedia) stopped working
Function keys should work
See https://bugzilla.kernel.org/show_bug.cgi?id=115021 where the fix were applied and also https://bugzilla.redhat.com/show_bug.cgi?id=1206862
I guess this happened when jumping from 4.11 to 4.12 right, not from 4.12.x to 4.12.9 ?
In that case it is probably best if you file a new bug upstream, pointing to the old bug and that it is broken again in 4.12, I expect upstream to know best what info they will need to debug this.
(In reply to Hans de Goede from comment #1)
> In that case it is probably best if you file a new bug upstream, pointing to
> the old bug and that it is broken again in 4.12, I expect upstream to know
> best what info they will need to debug this.
Follow upstream step for debugging:
All function keys first work with parameters from link above. After reboot, Fn keys somehow got restored. I am closing this bug for now as I can no longer reproduced it.
Reopening as I was able to reproduce the bug by closing and opening the lid from my laptop.
Created attachment 1330888 [details]
upstream patch used for the fix.
In summary, ECDT device is not registered as an ACPI device, so there is no driver binding against it. As a result, lock-up occurred between CPU hot plug and ACPI scan during the suspend process therefore EC functions like hotkeys failed.
Test was done on ASUS X550ZE and upstream provided the patch to solve the issue.
I am not if I should close this bug report now or should wait Fedora kernel team backport the patch until upstream kernel release.
Upstream just published the following patches:
addressing the issue related to ECDT devices not registered as ACPI. In my case, ASUS X550ZE was affected and it is likely almost all ASUS X series have similar symptom.
The 2nd patch in that series does not apply cleanly to the 4.13 series and the diffs are large enough this should be handled by the maintainers. Ideally this will happen through the regular stable process.
Thanks for the info. I will test future update once the maintainers applied the patches on stable.
(In reply to Laura Abbott from comment #7)
> The 2nd patch in that series does not apply cleanly to the 4.13 series and
> the diffs are large enough this should be handled by the maintainers.
> Ideally this will happen through the regular stable process.
Just following up about the status. Will it be possible to apply the patches from comment #6 for Rawhide i.e. 4.14 until the fixes landed on upstream kernel as the bug initially occurred on 4.12 to the current stable kernel? Thanks.
I just received an e-mail confirming the upstream fixes recently landed on 4.14.4 as highlighted below
Closing this bug as resolved.