Bug 218545 - Multiple distros crash and reboot when trying to resume from sleep/suspend on laptop
Summary: Multiple distros crash and reboot when trying to resume from sleep/suspend on...
Status: NEW
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: acpi_power-sleep-wake
URL:
Keywords:
Depends on: 178231
Blocks:
  Show dependency tree
 
Reported: 2024-03-01 17:49 UTC by richard
Modified: 2024-04-02 06:24 UTC (History)
1 user (show)

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


Attachments
from a few minutes after a suspend > crash > boot - dmesg on top and lspci at bottom (176.93 KB, text/plain)
2024-03-01 17:49 UTC, richard
Details

Description richard 2024-03-01 17:49:48 UTC
Created attachment 305939 [details]
from a few minutes after a suspend > crash > boot - dmesg on top and lspci at bottom

Gigabyte Aorus 15 XE4 laptop with Nvidia RTX 3070ti on latest BIOS. After multiple attempts, this doesn't seem to be related to Nvidia Drivers or intel/nvidia optimus like I thought based on many people with a similar issue.

Tested on:
    Ubuntu 22.04 Gnome Wayland
    Pop!_OS 22.04 Gnome Wayland
    Kubuntu 22.04 KDE Plasma Wayland, X11
    Manjaro 23 KDE Plasma Wayland, X11 (kernels 6.6.4, 6.8 experimental)
    KDE Neon Unstable with Plasma 6.0 Wayland

Have tried Nvidia drivers 470 and 545
Have tried disabling nvidia-suspend nvidia-hibernate nvidia-resume.
Also tried disabling split lock detection fix after seeing the logs.
Doesn't change if there is/isn't an external monitor attached.

Laptop appears to suspend fine as the breathing suspend led is active. Then upon opening or pressing power to wake, keyboard lights up and a second later the lights go out as system reboots. The screen does nothing until it boots from the crash. Issue persists on Intel, Hybrid, Nvidia GPU performance modes as well as using the Nouveau driver.
Comment 1 Armin Wolf 2024-04-02 06:24:06 UTC
Can you check if this still happens after blacklisting "vboxdrv"?

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