[Asus ZenBook UX325EA] Can't wake from sleep (when power adapter plugged in)

[Ernst Schoen-Rene]

on an Asus zenbook, 2022. When power is plugged in and screen goes to sleep, I can't get back, even with ctrl-alt-f1. I have to do a hard reboot.

Here's my uname:
Linux sleeky 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 4 17:21:51 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1452]
InstallationDate: Installed on 2023-01-13 (22 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX325EA_UX325EA
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=9d28c423-b126-49e5-9092-3ea7e2e68951 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX325EA.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX325EA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.8
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX325EA.308:bd07/29/2021:br5.19:efr3.8:svnASUSTeKCOMPUTERINC.:pnZenBookUX325EA_UX325EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX325EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX325EA_UX325EA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

Thanks for the bug report.

Next time the problem happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

[Ernst Schoen-Rene (ernstsr321)]

Here is the result of journalctl for the last boot. To make it fail, I go to settings > power > screen blank: 2min. I leave it plugged in and wait for the screen to go blank, and then I can no longer wake the laptop.

[Daniel van Vugt (vanvugt)]

Thanks. I can't see anything unusual going on and there are no log messages relating to this issue that I can see.

But I do see you're using non-atomic mode setting. That's not the default option so you must have enabled that in /etc/environment. Please re-enable atomic mode setting and repeat the steps in comment #2. It will either solve the bug or at least should log more errors about any failed display operations.

[Ernst Schoen-Rene (ernstsr321)]

Ah yes, I modified that to try to fix the problem, but no dice. I'll take it out and send you a new log.

[Ernst Schoen-Rene (ernstsr321)]

Yeah, I put that stuff in /etc/environment in attempt to fix the problem, but no dice.
Now that I know, this is a reliable bug. Power cord in, set "screen blank" to something besides "never", and let the screen go blank.

I commented the lines out of /etc/environment, rebooted, let the bug happen, and here is the journalctl output.

[Daniel van Vugt (vanvugt)]

I can't see anything to explain this still. Please check /var/crash for any evidence of crashes. You might also want to try some different kernel versions, although that requires disabling Secure Boot:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

Also I suspect bug 2006042 might be related.

[Ernst Schoen-Rene (ernstsr321)]

nothing in /var/crash

I don't think that there would be a crash, because I don't think the computer is crashing. It's going into some sort of sleep/standby mode and is unable to be awakened.

I just tried it hoping that I could ssh into the machine while it was in that mode, but I can't. The network is probably in some sort of hibernation mode too in this scenario.

[Daniel van Vugt (vanvugt)]

What does /proc/acpi/wakeup contain? It shows which system components are allowed to wake the machine from sleep.

[Ernst Schoen-Rene (ernstsr321)]

more /proc/acpi/wakeup
Device S-state Status Sysfs node
PEG1 S4 *disabled
PEGP S4 *disabled
PEG2 S4 *disabled
PEGP S4 *disabled
PEG3 S4 *disabled
PEGP S4 *disabled
PEG0 S4 *disabled
PEGP S4 *disabled
RP01 S4 *disabled
PXSX S4 *disabled
RP02 S4 *disabled
PXSX S4 *disabled
RP03 S4 *disabled
PXSX S4 *disabled
RP04 S4 *disabled
PXSX S4 *disabled
RP05 S4 *enabled pci:0000:00:1c.0
PXSX S4 *disabled pci:0000:57:00.0
  *disabled platform:rtsx_pci_sdmmc.0
RP06 S4 *disabled
PXSX S4 *disabled
RP07 S4 *disabled
PXSX S4 *disabled
RP08 S4 *disabled
PXSX S4 *disabled
RP09 S4 *disabled pci:0000:00:1d.0
PXSX S4 *disabled
RP10 S4 *disabled
PXSX S4 *disabled
RP11 S4 *disabled
PXSX S4 *disabled
RP12 S4 *disabled
PXSX S4 *disabled
RP13 S4 *disabled
PXSX S4 *disabled
RP14 S4 *disabled
PXSX S4 *disabled
RP15 S4 *disabled
PXSX S4 *disabled
RP16 S4 *disabled
PXSX S4 *disabled
RP17 S4 *disabled
PXSX S4 *disabled
RP18 S4 *disabled
PXSX S4 *disabled
RP19 S4 *disabled
PXSX S4 *disabled
RP20 S4 *disabled
PXSX S4 *disabled
RP21 S4 *disabled
PXSX S4 *disabled
RP22 S4 *disabled
PXSX S4 *disabled
RP23 S4 *disabled
PXSX S4 *disabled
RP24 S4 *disabled
PXSX S4 *disabled
XHCI S3 *enabled pci:0000:00:14.0
XDCI S4 *disabled
HDAS S4 *disabled pci:0000:00:1f.3
CNVW S4 *disabled pci:0000:00:14.3
TXHC S3 *enabled pci:0000:00:0d.0
TDM0 S3 *enabled pci:0000:00:0d.2
TDM1 S3 *enabled pci:0000:00:0d.3
TRP0 S3 *enabled pci:0000:00:07.0
PXSX S3 *disabled
TRP1 S3 *disabled
PXSX S3 *disabled
TRP2 S3 *enabled pci:0000:00:07.2
PXSX S3 *disabled
TRP3 S3 *disabled
PXSX S3 *disabled
AWAC S4 *enabled platform:ACPI000E:00

[Ernst Schoen-Rene (ernstsr321)]

Note that, as far as I can tell, this only happens when it's plugged in. When it's on battery power, it wakes from sleep fine.

[Daniel van Vugt (vanvugt)]

Sounds like the system has different sleep modes for battery vs AC. Since the above list mentions both S3 and S4 you might have some luck changing the sleep mode in the BIOS. Sometimes it's named strangely like "Windows" vs "Linux" sleep mode, but you can try both. The BIOS might also let you choose a different sleep mode for when plugged in.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Ernst Schoen-Rene (ernstsr321)]

Unfortunately, this computer has an incredibly hokey bios setup - seriously, it's like someone saw the matrix and decided they should add graphics to their bios like that - and it doesn't have any sleep mode settings or anything remotely related.

What are s4/s3 in the context you mention them?

[Daniel van Vugt (vanvugt)]

I'm not a power management or BIOS expert. I just know some sleep states work better than others, depending on the model of laptop.

https://en.wikipedia.org/wiki/ACPI#Power_states

[Ernst Schoen-Rene (ernstsr321)]

Is there any way to change the sleep state the os goes into? There's no way to change it in the bios.