https://bugzilla.kernel.org/show_bug.cgi?id=216838
Bug ID: 216838
Summary: ACPI events broken after deep sleep
Product: ACPI
Version: 2.5
Kernel Version: 6.1.1 (and 5.19.0)
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: acpi_ot...@kernel-bugs.osdl.org
Reporter: axk...@gmail.com
Regression: No
Created attachment 303462
--> https://bugzilla.kernel.org/attachment.cgi?id=303462&action=edit
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)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
