Acer Aspire AV15-51 | Suspend Issue

User Support
1

Hello everyone,

Firstly, thanks to all the community of Qubes that allowed me to install Qubes and have it properly running.
Here my qubes HCL report:

layout:
  'hcl'
type:
  'Notebook'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  '2.0'
remap:
  'yes'
brand: |
  Acer
model: |
  Aspire AV15-51
bios: |
  V1.08
cpu: |
  11th Gen Intel(R) Core(TM) i5-1155G7 @ 2.50GHz
cpu-short: |
  FIXME
chipset: |
  00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 02)
chipset-short: |
  FIXME
gpu: |
  02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 03) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 [8086:a0f0] (rev 30)
  00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
memory: |
  16163
scsi: |

usb: |
  1
certified:
  'no'
versions:
  - works:
      'FIXME:yes|no|partial'
    qubes: |
      R4.2.3
    xen: |
      4.17.5
    kernel: |
      6.6.48-1
    remark: |
      FIXME
    credit: |
      FIXAUTHOR
    link: |
      FIXLINK

I have suspend/resume issue and after searching for a solution for a couple of days I saw that it is quite common for Qubes. Solving this issue seems quite complicated considering all the different hardwares possible, so I know there is very little chance that it will work. I created this topic to add something to the database and, if a miracle happen, to describe a solution in a Qubes HCL report.

Shortly, to not waste everyone’s time, here is what I have tried and what I know:

  • S3 is supported (ACPI: PM: (supports S0 S3 S5)).
  • I added mem_sleep_default=deep to /etc/default/grub.
  • I cannot disable hyperthreading in the BIOS.
  • When I try to suspend a qube from the command line (systemctl suspend), then the qube crashes and I cannot shut id down (I have to poweroff the computer).
  • Choosing Lock screen when closing the laptop works, and I see both Lid closed and Lid opened in the journal.
  • Finally, I tried to have some information from journalctl to see what happens, so I tried to do something precise and read the journal:
Time Action Computer
0m Closing the lid Screen & Vents shutdown
5m Opening the lid Vents go on
10m Pressing keys, Enter, Escape, etc. Keyboard light goes on
15m Shutting down with power button Shuts down
20m Powering on Powers on

And here is the journal:

Oct 23 17:05:06 dom0 systemd-logind[1902]: Lid closed.
Oct 23 17:05:09 dom0 systemd[1]: /usr/lib/systemd/system/qubes-suspend.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, a>
Oct 23 17:05:09 dom0 systemd[1]: /usr/lib/systemd/system/qubes-suspend.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, a>
Oct 23 17:05:09 dom0 systemd[1]: Starting qubes-suspend.service - Qubes suspend hooks...
Oct 23 17:05:09 dom0 pkexec[5033]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
Oct 23 17:05:09 dom0 audit[5033]: USER_START pid=5033 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/pkexec>
Oct 23 17:05:09 dom0 kernel: audit: type=1105 audit(1729695909.112:347): pid=5033 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix acct>
Oct 23 17:05:09 dom0 pkexec[5033]: user Executing command [USER=root] [TTY=unknown] [CWD=/home/user] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brightness 5575]
Oct 23 17:05:10 dom0 52qubes-pause-vms[5045]: 0
Oct 23 17:05:10 dom0 systemd[1]: Finished qubes-suspend.service - Qubes suspend hooks.
Oct 23 17:05:10 dom0 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Oct 23 17:05:10 dom0 systemd[1]: Reached target sleep.target - Sleep.
Oct 23 17:05:10 dom0 kernel: audit: type=1130 audit(1729695910.842:348): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hos>
Oct 23 17:05:10 dom0 systemd[1]: Starting systemd-suspend.service - System Suspend...
Oct 23 17:05:10 dom0 systemd-sleep[5065]: Entering sleep state 'suspend'...
Oct 23 17:05:10 dom0 kernel: PM: suspend entry (deep)
-- Boot 49c8a3f33dfd459b9c41eb603eefd9ff --
Oct 23 17:25:38 localhost kernel: Linux version 6.6.48-1.qubes.fc37.x86_64 (mockbuild@065a31b3c1ba4c34ab3938416488814f) (gcc (GCC) 12.3.1 20230508 (Red Hat 12.3.1-1), GNU ld version 2.38-27>
Oct 23 17:25:38 localhost kernel: Command line: placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-228a9d0e-62f0-42d0-a2ac-67448ff479e7 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qu>
Oct 23 17:25:38 localhost kernel: Released 0 page(s)
Oct 23 17:25:38 localhost kernel: BIOS-provided physical RAM map:
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000000000000-0x000000000007ffff] usable
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000000080000-0x00000000000fffff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000000100000-0x000000003fd98fff] usable
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x000000003fd99000-0x0000000040698fff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000040699000-0x00000000424aefff] usable
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000424af000-0x00000000442fefff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000442ff000-0x0000000044b2efff] ACPI NVS
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000044b2f000-0x0000000044bfefff] ACPI data
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000044bff000-0x0000000044bfffff] usable
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000044c00000-0x0000000048ffffff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000049e00000-0x000000004f7fffff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000fe010000-0x00000000fe010fff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000fed90000-0x00000000fed91fff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x00000000ff500000-0x00000000ffffffff] reserved
Oct 23 17:25:38 localhost kernel: Xen: [mem 0x0000000100000000-0x00000001be4cffff] usable
Oct 23 17:25:38 localhost kernel: NX (Execute Disable) protection: active
Oct 23 17:25:38 localhost kernel: APIC: Static calls initialized
Oct 23 17:25:38 localhost kernel: efi: EFI v2.7 by INSYDE Corp.
Oct 23 17:25:38 localhost kernel: efi: ACPI=0x44bfe000 ACPI 2.0=0x44bfe014 TPMFinalLog=0x44ac5000 SMBIOS=0x429de000 SMBIOS 3.0=0x429dc000 (MEMATTR=0x3bdbe018 unusable) ESRT=0x44b78018 
Oct 23 17:25:38 localhost kernel: SMBIOS 3.3.0 present.
Oct 23 17:25:38 localhost kernel: DMI: Acer Aspire AV15-51/Jade_TL, BIOS V1.08 08/23/2023
Oct 23 17:25:38 localhost kernel: Hypervisor detected: Xen PV
Oct 23 17:25:38 localhost kernel: tsc: Fast TSC calibration using PIT
Oct 23 17:25:38 localhost kernel: tsc: Detected 2495.998 MHz processor
Oct 23 17:25:38 localhost kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 23 17:25:38 localhost kernel: e820: remove [mem 0x000a0000-0x000fffff] usable

and then the computer just works normally.
So, literally nothing happens in the journal while suspending it, and I have absolutely no clue of why it is not working. What else can I do to have more information on what is happening?

(Topic removed & reopend because of finger trouble).