Bug 216854 - Microsoft Surface Laptop 5 has trouble to wake up from suspend by opening the lid, lots of ACPI errors
Summary: Microsoft Surface Laptop 5 has trouble to wake up from suspend by opening the...
Status: NEW
Alias: None
Product: ACPI
Classification: Unclassified
Component: ACPICA-Core (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_acpica-core@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-27 20:13 UTC by mbrennwa
Modified: 2022-12-27 20:13 UTC (History)
0 users

See Also:
Kernel Version: 6.0.12
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg output (259.27 KB, text/plain)
2022-12-27 20:13 UTC, mbrennwa
Details

Description mbrennwa 2022-12-27 20:13:18 UTC
Created attachment 303489 [details]
dmesg output

Hello

I am running Debian SID on my Microsoft Surface Laptop 5 using the Surface specific kernel from https://github.com/linux-surface/linux-surface. After suspending the machine by closing the lid, it has trouble with waking up when I re-open the lid (note: this is not an issue if I suspend the machine by other means, for example using the GNOME power menu):

- Once I open the lid, the keyboard light will turn on, but the screen usually remains black (with some rare and apparently erratic exceptions, when the screen turns on fine).

- If I wait a few seconds until the keyboard lights turn off again and then press any key (not the power button), the screen usually turns on and the machine works as expected (with some rare and apparently erratic exceptions, when the screen remains black).

- Running `sudo dmesg` right after such a lid-close/suspend/lid-open/wake-up cycle produced the output in the attachment. Note that the ACPI error `Could not disable RealTimeClock events` also occurs at boot (not shown in the attachment).

I have already reported and discussed this issue with the maintainer of the Surface specific kernel at https://github.com/linux-surface/linux-surface/issues/1010, who concluded that this issue should be reported upstream (here).

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