Acer Swift SF114-34 standby/suspend/resume issue

[pbuzas]

When I close the lid the laptop does not go to standby.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pbuzas 2163 F.... pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-04-11 (90 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
 Bus 001 Device 003: ID 1c7a:0575 LighTuning Technology Inc. EgisTec EH575
 Bus 001 Device 002: ID 0408:a094 Quanta Computer, Inc. HD User Facing
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Swift SF114-34
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-40-generic N/A
 linux-backports-modules-5.15.0-40-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.2
Tags: wayland-session jammy
Uname: Linux 5.15.0-40-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.11
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Labatt_JL
dmi.board.vendor: JSL
dmi.board.version: V1.11
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/02/2021:br1.11:efr1.11:svnAcer:pnSwiftSF114-34:pvrV1.11:rvnJSL:rnLabatt_JL:rvrV1.11:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Swift 1
dmi.product.name: Swift SF114-34
dmi.product.sku: 0000000000000000
dmi.product.version: V1.11
dmi.sys.vendor: Acer

[pbuzas (peter-buzas)]

Latest 1.11 BIOS is installed on the system:

pbuzas@SF114:~$ sudo dmidecode -t system
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
 Manufacturer: Acer
 Product Name: Swift SF114-34
 Version: V1.11

[pbuzas (peter-buzas)]

Issuing the following commands as root fixes the issue until reboot:

echo RP05 > /proc/acpi/wakeup
echo XHCI > /proc/acpi/wakeup

It would be nice if Ubuntu 22.04 would provide suspend/resume support without having to enter these commands after every reboot.

[pbuzas (peter-buzas)]

I tried following the debugging steps here:
https://wiki.ubuntu.com/DebuggingKernelSuspend

However when issuing the following command:

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

I get this:

pbuzas@SF114:~$ sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
sh: 1: pm-suspend: not found

[pbuzas (peter-buzas)]

1. Which part of the process does the issue occur with, the suspend to ram, or resuming from?

Issue seems to be that laptop does not do suspend to ram when closing the lid.

2. Please advise how you suspended specifically. For example:
Executing at a terminal pm-suspend
Shutting the lid of your laptop, which is set to suspend on close.
Clicking the word Suspend in the GUI.
The computer suspends automatically on inactivity.

I tried suspending by shutting/closing the lid of the laptop. If the laptop is suspended then the power led turns from blue to amber/orange, this is not happening, it just blinks once but remains blue.

3. Please advise how you resumed specifically. For example:
Pressed the power button
Lifted the lid
Clicked a key on the keyboard

I lifted/opened the lid. I was presented the login screen.

4. While booted into the latest non-daily mainline kernel, execute at a terminal:

cat /proc/acpi/wakeup > wakeup

After executing this, perform a pm_trace and attach the results to your report.

I issued the above mentioned commands, the cat command had no output, pm_trace is not found.

5. While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo freezer > /sys/power/pm_test
exit
After executing this, perform a pm_trace and attach the results to your report.

I was able to execute the echo command as root, pm_trace is still not found.

6. While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo devices > /sys/power/pm_test
exit
After executing this, perform a pm_trace and attach the results to your report.

I was able to execute the echo command as root, pm_trace is still not found.

7. While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo platform > /sys/power/pm_test
exit
After executing this, perform a pm_trace and attach the results to your report.

I was able to execute the echo command as root, pm_trace is still not found.

8. While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo processors > /sys/power/pm_test
exit
After executing this, perform a pm_trace and attach the results to your report.

I was able to execute the echo command as root, pm_trace is still not found.

9. While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo core > /sys/power/pm_test
exit
After executing this, perform a pm_trace and attach the results to your report.

I was able to execute the echo command as root, pm_trace is still not found.

10. While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo none > /sys/power/pm_test
exit
After executing this, perform a pm_trace and attach the results to your report.

I was able to execute the echo command as root, pm_trace is still not found.

11. Please provide the output of the following terminal command:

cat /sys/kernel/debug/suspend_stats

pbuzas@SF114:~$ sudo cat /sys/kernel/debug/suspend_stats
success: 3
fail: 0
failed_freeze: 0
failed_prepare: 0
failed_suspend: 0
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
 ...

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1981141/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[pbuzas (peter-buzas)]

I updated the package and description.

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1981141

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

apport information

[pbuzas (peter-buzas)]

I ran the apport collect that ended with a dpkg-query error suggesting linux package was not found. However it seems apport did collect some information, I hope this will be enough to progress the troubleshooting.

[pbuzas (peter-buzas)]

Currently I have the extra commands I mentioned above in effect that seems to fix the issue:

echo RP05 > /proc/acpi/wakeup
echo XHCI > /proc/acpi/wakeup

If I issue these as root then suspend/resume seems to work as it should until next reboot.

[pbuzas (peter-buzas)]

I still see this bug showing as 'Incomplete'. Could someone advise what additional information I need to provide?

[pbuzas (peter-buzas)]

As suggested on the related question thread I am setting the status to 'Confirmed'.

[dvo (mueller8)]

This bug is still present in Ubuntu 22.04.4 LTS with current patches.

I'm glad to have found the workaround mentioned above.