Hi, On 7/29/24 1:23 PM, Hans de Goede wrote: > Hi, > > On 7/22/24 5:35 PM, Iñaki Ucar wrote: >> >> On Mon, 22 Jul 2024 at 17:22, Iñaki Ucar <iucar@xxxxxxxxxxxxxxxxx <mailto:iucar@xxxxxxxxxxxxxxxxx>> wrote: >> >> Hi Hans, >> >> On Thu, 18 Jul 2024 at 11:28, Hans de Goede <hdegoede@xxxxxxxxxx <mailto:hdegoede@xxxxxxxxxx>> wrote: >> >> Hi, >> >> On 7/16/24 5:59 PM, Iñaki Ucar wrote: >> > >> > >> > On Tue, 16 Jul 2024 at 12:29, Hans de Goede <hdegoede@xxxxxxxxxx <mailto:hdegoede@xxxxxxxxxx> <mailto:hdegoede@xxxxxxxxxx <mailto:hdegoede@xxxxxxxxxx>>> wrote: >> > >> > Hi, >> > >> > On 7/15/24 9:50 PM, Iñaki Ucar wrote: >> > > It's the kernel. Going back to 6.9.6 fixes the issue... >> > >> > Ok, that is a good first step in debugging this. >> > >> > Can you run evtest with the working kernel and then check which >> > event node is generating key-presses for the brightness keys, >> > that should help narrow it down further. >> > >> > Likely candidates are: "LG WMI hotkeys", >> > "AT translated set 2 keyboard", "Video Bus". >> > >> > >> > In "Video Bus", there are KEY_BRIGHTNESSDOWN and KEY_BRIGHTNESSUP that are triggered. >> >> Ok, then this likely is not an issue with the lg-laptop driver but rather with >> the ACPI subsystem. >> >> Likely culprit commits which are new in 6.9.7 are: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi?h=v6.9.7&id=2b2b0ac1533d790690d6d28899f01a2924d54d4d <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi?h=v6.9.7&id=2b2b0ac1533d790690d6d28899f01a2924d54d4d> >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi?h=v6.9.7&id=9750135f2f326879889ed60ccd68b96572dfa6ee <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi?h=v6.9.7&id=9750135f2f326879889ed60ccd68b96572dfa6ee> >> >> >> Or maybe: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi?h=v6.9.7&id=e21a4c9129c72fa54dd00f5ebf71219b41d43c04 <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi?h=v6.9.7&id=e21a4c9129c72fa54dd00f5ebf71219b41d43c04> >> >> But I suspect it is one of the above 2. >> >> I have started a 6.9.9 test-build with those 2 patches reverted: >> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=120674294 <https://koji.fedoraproject.org/koji/taskinfo?taskID=120674294> >> >> >> Good catch! I confirm that the build above does not have the issues I was experiencing. > > Thank you I have reported this issue to the ACPI maintainer now: > > https://lore.kernel.org/linux-acpi/1f76b7e2-1928-4598-8037-28a1785c2d13@xxxxxxxxxx/ > > >> However, with this I have another issue: when I connect my laptop to my Thunderbolt dock, I see irq/9-acpi constantly spinning the CPU at 40%. :( I had to go back to the previous one. > > Ok, that is unfortunate. Can you try powering off the lapto and then directly booting into the test kernel, > without first booting a bad kernel? I'm wondering if the bad kernel maybe confuses the EC in such a way > that it is still unhappy after a reboot. Also can you please file a bug for this here: https://bugzilla.kernel.org/enter_bug.cgi?product=ACPI (creating an account only requires an email address + your name, no other info is requires). As ACPI sub component please select "EC". and then please run: sudo dnf install acpica-tools sudo acpidump > acpidump.txt And attach the generated acpidump.txt file to the bug you have created at: https://bugzilla.kernel.org/ This gives us access to a copy of the ACPI tables of your laptop which will hopefully help with debugging this further. Regards, Hans -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
