Created attachment 292221 [details] ACPI tables In Linux, S3 sleep state seems to be unavailable for RedmiBook 16. $ cat /sys/power/mem_sleep [s2idle] What's strange is that the Kernel seems to detect 3 states when booting. $ dmesg | grep "idle state" [ 0.694581] ACPI: \_SB_.PLTF.C000: Found 3 idle states [ 0.694859] ACPI: \_SB_.PLTF.C001: Found 3 idle states [ 0.695178] ACPI: \_SB_.PLTF.C002: Found 3 idle states [ 0.695355] ACPI: \_SB_.PLTF.C003: Found 3 idle states [ 0.695509] ACPI: \_SB_.PLTF.C004: Found 3 idle states [ 0.695658] ACPI: \_SB_.PLTF.C005: Found 3 idle states [ 0.695809] ACPI: \_SB_.PLTF.C006: Found 3 idle states [ 0.695959] ACPI: \_SB_.PLTF.C007: Found 3 idle states Deep sleep seems to work in Windows which seems to suggest it's simply a case of lack of Linux support. I've attached a dump of this device's ACPI tables and can provide logs and other dumps as needed.
(In reply to Rasmus Moorats from comment #0) > Created attachment 292221 [details] > ACPI tables > > In Linux, S3 sleep state seems to be unavailable for RedmiBook 16. > > $ cat /sys/power/mem_sleep > [s2idle] I don't think this is a bug. It just suggests that S3 is not supported on this platform. > > What's strange is that the Kernel seems to detect 3 states when booting. > > $ dmesg | grep "idle state" > [ 0.694581] ACPI: \_SB_.PLTF.C000: Found 3 idle states > [ 0.694859] ACPI: \_SB_.PLTF.C001: Found 3 idle states > [ 0.695178] ACPI: \_SB_.PLTF.C002: Found 3 idle states > [ 0.695355] ACPI: \_SB_.PLTF.C003: Found 3 idle states > [ 0.695509] ACPI: \_SB_.PLTF.C004: Found 3 idle states > [ 0.695658] ACPI: \_SB_.PLTF.C005: Found 3 idle states > [ 0.695809] ACPI: \_SB_.PLTF.C006: Found 3 idle states > [ 0.695959] ACPI: \_SB_.PLTF.C007: Found 3 idle states > These are CPU cstates, and these messages show there are 3 ACPI Cstate supported, so this is not a bug. > Deep sleep seems to work in Windows which seems to suggest it's simply a > case of lack of Linux support. > TBH, I don't think so. May I know is it windows on modern Intel platforms usually uses s0ix as system low power state, and Linux s2idle does the same thing. Bug closed as I don't see any problem from the description above. But if there are some issues like high power consumption during system sleep, then that sounds like a real issue and feel free to re-open this bug report.