Bug 216838 - ACPI events broken after deep sleep
Summary: ACPI events broken after deep sleep
Status: NEW
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: acpi_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-23 13:47 UTC by Axel Kittenberger
Modified: 2022-12-23 13:47 UTC (History)
0 users

See Also:
Kernel Version: 6.1.1 (and 5.19.0)
Subsystem:
Regression: No
Bisected commit-id:


Attachments
acpidump > acpidata.dat (2.37 MB, text/plain)
2022-12-23 13:47 UTC, Axel Kittenberger
Details

Description Axel Kittenberger 2022-12-23 13:47:53 UTC
Created attachment 303462 [details]
acpidump > acpidata.dat

After resuming from "deep" suspend, ACPI events seem to be messed up. Brightness modifiers procude following log output instead:

[   76.252190] atkbd serio0: Unknown key pressed (translated set 2, code 0x64 on isa0060/serio0).
[   76.252200] atkbd serio0: Use 'setkeycodes 64 <keycode>' to make it known.
[   76.870082] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0).
[   76.870092] atkbd serio0: Use 'setkeycodes 65 <keycode>' to make it known.

They worked before deep suspenion, and survive s2sleep as well. And even more annoyingly the lidswitch doesn't do anything after the first deep suspend.

Device: ASUS expertbook-b5-flip-b5302f, latest BIOS 310

My guess it's something messed up in their BIOS, but wonder if it can be worked around (as other issues, like https://bugzilla.kernel.org/show_bug.cgi?id=216101 have workarounds)

I tried to get deep sleep working, since s2idle did use about 10-20% battery per day (tested with 5.19.0 and VMD active, have to do more tests with 6.1.1 and VMD off to tell more on that route)

Note You need to log in before you can comment on or make changes to this bug.