Black screen after resuming from sleep

grubmkconfig · 2024-10-14 23:29:26

I also wanted to add here that I have a very similar system and have been facing this issue after upgrading to the 6.11 kernel. I dual boot Windows but have fastboot turned off. My hardware is: Ryzen CPU, Radeon graphics, NVME SSD boot drive, which sounds similar to some others in this thread. I also see a successful "Successfully froze unit 'user.slice'" message from systemd in my logs. For now, I have downgraded to 6.10 but have a 6.11 kernel loaded to try any possible fixes/logging. My test 6.11 kernel was vanilla Linux so I'm confident this is an upstream issue.

Edit: turning off bluetooth before sleep fixes my issue on 6.11.3 so that was likely the cause. Thanks!

Last edited by grubmkconfig (2024-10-14 23:34:25)

cstdio · 2024-10-15 04:21:53

For me rfkill and

systemctl bluetooth disable

only makes the next sleep cycle normal but disabling wifi and bluetooth in UEFI works.

seth · 2024-10-15 07:05:48

mt7921e has a loooong history causing all sorts of issues, but the concerted systematic failure introduced in 6.11 is
https://bugzilla.kernel.org/buglist.cgi … ch=mt7921e

Does adding

mt7921e.disable_aspm=Y

to the https://wiki.archlinux.org/title/Kernel_parameters help?

gerwazy · 2024-10-15 09:02:32

Today new update nvidia-utils

If you run into trouble with CUDA not being available, run nvidia-modprobe first.
If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
If you use sleep on wayland, you might have to run systemctl enable nvidia-resume nvidia-hibernate nvidia-suspend

But beware - this applies not only to Wayland, as the post above suggests, but also to Xorg.

cstdio · 2024-10-15 17:02:49

Only using

mt7921e.disable_aspm=Y

also works.

seth · 2024-10-15 19:17:31

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

If this doesn't get fixed with one of the next kernels, you probably want to file a bug, but as mentioned, mt7921e has a long history itr, so I'd not hold my breath

rkolbaskin · 2024-10-16 03:19:41

Doesn't work for me. I have MT7921K (RZ608) and even with mt7921e.disable_aspm=Y having Bluetooth enabled leads to lockup at resume.

cstdio · 2024-10-16 03:23:29

Can confirm having bluetooth enabled also leads to failed sleep cycle. I never had it enabled by default so I didn't notice that before

Edit: just tested enabling either wifi or bluetooth in kde settings causes the issue to come back.
Also it's interesting even with bluetooth disabled in UEFI, kde settings still has the option to enable bluetooth and causes the sleep problem. Although in UEFI settings the option is BT On/Off with no further explanation so technically it could be anything...

Do I mark it as solved or not solved?

Last edited by cstdio (2024-10-16 03:53:25)

seth · 2024-10-16 07:03:53

Although in UEFI settings the option is BT On/Off with no further explanation so technically it could be anything...

Does BT still show up in rfkill when disabling it in the UEFI?

If disabling the mt7921e aspm doesn't actually fix it, it's not technically solved, since the only solution is to (use the LTS kernel or) remove that NIC.

gerwazy · 2024-10-16 17:40:36

Solved for me

Last edited by gerwazy (2024-10-16 18:07:35)

cstdio · 2024-10-16 20:28:48

Yeah bluetooth still shows up in rfkill. I couldn't find other options in UEFI that are related to bluetooth though.

So to summarize the current situation: disable wifi in UEFI or disable mt7921e works. However as soon as bluetooth is enabled the problem returned.

seth · 2024-10-16 20:37:16

The BIOS settings will only define the initial rfkill state then.
Does it suffice to rfkill the BT device before the suspend and either
a) mt7921e.disable_aspm=Y
b) rfkill the wifi as well
?

cstdio · 2024-10-16 21:10:15

For wifi once I disabled it in UEFI it doesn't show up in rfkill.

rfkill the wifi, bluetooth or both without any other step only makes the next sleep cycle work.
mt7921e.disable_aspm=Y itself works as long as bluetooth is not enabled. wifi does not change results

Last edited by cstdio (2024-10-16 21:15:38)

seth · 2024-10-16 21:22:56

rfkill the wifi, bluetooth or both without any other step only makes the next sleep cycle work.

The plan was to https://man.archlinux.org/man/core/util … fkill.8.en the devices right before each sleep cycle and in doubt rf-un-kill it afterwards.

cstdio · 2024-10-16 21:29:56

cstdio wrote:

Unfortunately for me blocking wifi and bluetooth only makes the next sleep cycle work. Even if I rfkill again after waking up the second sleep cycle is still stuck and needs a reboot.

I tried it the other day to rfkill wifi and bluetooth before each sleep cycle and it only works the first try. I could try it again later today to see if anything magically changed.

seth · 2024-10-16 21:51:11

The only thing to test would be "mt7921e.disable_aspm=Y" plus rf-cycling bluetooth, the latter preferably on the disabled setting in the BIOS (it's odd that you can/have to do this after the wakeup and from all I've heard I guess the BIOS setting also dictates the wakeup rfkill state for BT) ie.
1. "mt7921e.disable_aspm=Y"
2. "disable" BT in the BIOS
3. enable BT via rfkill during the boot
4. disable BT via rfkill
5. sleep the system
6. wake the system
7. profit?

cstdio · 2024-10-17 01:18:44

So I decided to do some more tests and found out the followings:
Without any change to UEFI or "mt7921e.disable_aspm=Y", by simply disabling bluetooth through KDE settings sleep works. This method is reliable in the sense that as long as it is disabled, no matter what the previous state is sleep will work.
If bluetooth is enabled and then disabled using rfkill, the next sleep works. However, on second try even if "rfkill block bluetooth" is used again sleep does not work.
Wifi has no effect on anything.

Seems like the issue is purely bluetooth and somehow KDE settings is more reliable than rfkill (or something is messing with rfkill somehow)? Also mt7921e might not be the cause after all.

Edit:
This is the journalctl of the first "rfkill block bluetooth"

Oct 16 21:17:33 archlinux sudo[2775]: pam_systemd_home(sudo:auth): New sd-bus connection (system-bus-pam-systemd-home-2775) opened.
Oct 16 21:17:41 archlinux sudo[2775]:   cstdio : TTY=pts/1 ; PWD=/home/cstdio ; USER=root ; COMMAND=/usr/bin/rfkill block bluetooth
Oct 16 21:17:41 archlinux sudo[2775]: pam_unix(sudo:session): session opened for user root(uid=0) by cstdio(uid=1000)
Oct 16 21:17:41 archlinux rfkill[2782]: block set for type bluetooth
Oct 16 21:17:41 archlinux sudo[2775]: pam_unix(sudo:session): session closed for user root
Oct 16 21:17:41 archlinux systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 16 21:17:41 archlinux systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 16 21:17:46 archlinux systemd[1]: systemd-rfkill.service: Deactivated successfully.

This is the journalctl of the second "rfkill block bluetooth" after first successful sleep

Oct 16 21:19:37 archlinux kernel: Bluetooth: hci0: Device setup in 20460222 usecs
Oct 16 21:19:37 archlinux kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Oct 16 21:19:37 archlinux kernel: Bluetooth: hci0: AOSP extensions version v1.00
Oct 16 21:19:37 archlinux kernel: Bluetooth: hci0: AOSP quality report is supported
Oct 16 21:19:37 archlinux bluetoothd[686]: Battery Provider Manager created
Oct 16 21:19:37 archlinux kernel: Bluetooth: MGMT ver 1.23
Oct 16 21:19:37 archlinux bluetoothd[686]: Failed to set mode: Failed (0x03)
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/ldac
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aptx_hd
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_hd
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aptx
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aac
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aac
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_g
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_g
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream_duplex
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Oct 16 21:19:37 archlinux bluetoothd[686]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Oct 16 21:19:38 archlinux bluetoothd[686]: Failed to set mode: Failed (0x03)
Oct 16 21:19:38 archlinux kded6[1143]: kf.bluezqt: PendingCall Error: "Failed"
Oct 16 21:19:51 archlinux sudo[3163]: pam_systemd_home(sudo:account): New sd-bus connection (system-bus-pam-systemd-home-3163) opened.
Oct 16 21:19:51 archlinux sudo[3163]:   cstdio : TTY=pts/1 ; PWD=/home/cstdio ; USER=root ; COMMAND=/usr/bin/rfkill block bluetooth
Oct 16 21:19:51 archlinux sudo[3163]: pam_unix(sudo:session): session opened for user root(uid=0) by cstdio(uid=1000)
Oct 16 21:19:51 archlinux rfkill[3166]: block set for type bluetooth
Oct 16 21:19:51 archlinux sudo[3163]: pam_unix(sudo:session): session closed for user root

seems like there's error in bluetoothd and rfkill never actually disables bluetooth.

However toggling bluetooth in KDE settings seems fine

Oct 16 21:23:22 archlinux systemsettings[2576]: kf.bluezqt: PendingCall Error: ""
Oct 16 21:23:22 archlinux systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 16 21:23:22 archlinux systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 16 21:23:22 archlinux kernel: Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240716163633
Oct 16 21:23:22 archlinux kernel: Bluetooth: hci0: Device setup in 185879 usecs
Oct 16 21:23:22 archlinux kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Oct 16 21:23:22 archlinux kernel: Bluetooth: hci0: AOSP extensions version v1.00
Oct 16 21:23:22 archlinux kernel: Bluetooth: hci0: AOSP quality report is supported
Oct 16 21:23:27 archlinux systemd[1]: systemd-rfkill.service: Deactivated successfully.
Oct 16 21:23:27 archlinux systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 16 21:23:27 archlinux systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 16 21:23:32 archlinux systemd[1]: systemd-rfkill.service: Deactivated successfully.

second edit: seems like running rfkill as non root works.

Last edited by cstdio (2024-10-17 05:03:34)

seth · 2024-10-17 07:26:35

So bottom line is that "mt7921e.disable_aspm=Y" and rfkill'ing bluetooth ahead of the sleep works.

Remaining problem in order to work around this (again, mt7921e has many issues for a long time, so Curb Your Enthusiasm) would be to effectively rfkill BT - maybe b/c bluetoothd is in the way?
Did you try to actively unblock BT after the suspend and before the next block?
Your second journal snippet doesn't so much show a failure to block it but more bluetoothd complaining around, likely because BT already was blocked?

cstdio · 2024-10-17 17:44:47

Without "mt7921e.disable_aspm=Y" and just blocking bluetooth also works.

Yes. It doesn't matter how many times bluetooth is enabled, as long as it is disabled when suspend happens it works. It's just that I ran

sudo rfkill block bluetooth

before and somehow this only makes the next immediate sleep works even if I run it before every sleep. However running it as

rfkill block bluetooth

only once (or repeat before every sleep) makes every sleep cycle work.

rkolbaskin · 2024-10-18 10:40:41

If you needed any more confirmation that MediaTek wireless card is to blame - I just replaced mine with AX210 and the problem seems to be gone.

monkeyvsmonkey · 2024-10-24 09:09:43

I am technically not on arch but I get the same behaviour and it broke for me on 6.11 as well. So for now I will go back to using 6.10

Hardware info:

Operating System: EndeavourOS x86_64
KDE Plasma Version: KDE Plasma 6.2.1
Kernel Version: Linux 6.11.5-arch1-1
WM: KWin (Wayland)
CPU: AMD Ryzen 9 7950X3D (32) @ 5.76 GHz
GPU 1: AMD Radeon RX 7900 GRE [Discrete]
GPU 2: AMD Raphael [Integrated]
Memory: 64 GiB
Swap: Disabled
Motherboard: Asus ROG STRIX B650E-F GAMING WIFI ATX

Device           Start        End    Sectors  Size Type
/dev/nvme0n1p1    4096    2101247    2097152    1G EFI System
/dev/nvme0n1p2 2101248 3907024064 3904922817  1.8T Linux filesystem

Log from last boot:

Oct 23 18:42:12 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=960700
Oct 23 18:42:12 mother-base rtkit-daemon[2484]: Supervising 10 threads of 7 processes of 1 users.
Oct 23 18:42:12 mother-base rtkit-daemon[2484]: Supervising 10 threads of 7 processes of 1 users.
Oct 23 18:42:15 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=960700
Oct 23 18:42:18 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=960700
Oct 23 18:42:21 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-51 noise=9999 txrate=960700
Oct 23 18:42:24 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=960700
Oct 23 18:42:27 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=960700
Oct 23 18:42:30 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=960700
Oct 23 18:42:33 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=960700
Oct 23 18:42:36 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=960700
Oct 23 18:42:38 mother-base systemd-logind[2146]: The system will suspend now!
Oct 23 18:42:38 mother-base NetworkManager[2173]: <info>  [1729701758.8180] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Oct 23 18:42:38 mother-base NetworkManager[2173]: <info>  [1729701758.8293] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Oct 23 18:42:38 mother-base NetworkManager[2173]: <info>  [1729701758.8295] manager: NetworkManager state is now ASLEEP
Oct 23 18:42:38 mother-base NetworkManager[2173]: <info>  [1729701758.8295] device (wlan0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Oct 23 18:42:38 mother-base kded6[2637]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Oct 23 18:42:38 mother-base systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 23 18:42:38 mother-base systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 23 18:42:38 mother-base kernel: wlan0: deauthenticating from 7a:45:58:39:eb:1e by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 23 18:42:39 mother-base wpa_supplicant[2299]: nl80211: send_event_marker failed: Source based routing not supported
Oct 23 18:42:39 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-DISCONNECTED bssid=7a:45:58:39:eb:1e reason=3 locally_generated=1
Oct 23 18:42:39 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.3685] device (wlan0): supplicant interface state: completed -> disconnected
Oct 23 18:42:39 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-9999 noise=9999 txrate=0
Oct 23 18:42:39 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.3686] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Withdrawing address record for fe80::373f:b602:9c26:b86d on wlan0.
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::373f:b602:9c26:b86d.
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.3688] dhcp4 (wlan0): canceled DHCP transaction
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.3688] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.3688] dhcp4 (wlan0): state changed no lease
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.47.
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Withdrawing address record for 192.168.1.47 on wlan0.
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.4689] device (wlan0): set-hw-addr: set MAC address to 6A:A6:6C:97:DE:0D (scanning)
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.47.
Oct 23 18:42:39 mother-base avahi-daemon[2142]: New relevant interface wlan0.IPv4 for mDNS.
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Registering new address record for 192.168.1.47 on wlan0.IPv4.
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Withdrawing address record for 192.168.1.47 on wlan0.
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.47.
Oct 23 18:42:39 mother-base avahi-daemon[2142]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.6193] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.6194] device (wlan0): supplicant interface state: interface_disabled -> disconnected
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.6195] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Oct 23 18:42:39 mother-base NetworkManager[2173]: <info>  [1729701759.7307] device (wlan0): set-hw-addr: reset MAC address to 4C:82:A9:92:EA:D3 (unmanage)
Oct 23 18:42:39 mother-base wpa_supplicant[2299]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 23 18:42:39 mother-base systemd[1]: Reached target Sleep.
Oct 23 18:42:39 mother-base systemd[1]: Starting NVIDIA system suspend actions...
Oct 23 18:42:39 mother-base suspend[29035]: nvidia-suspend.service
Oct 23 18:42:39 mother-base logger[29035]: <13>Oct 23 18:42:39 suspend: nvidia-suspend.service
Oct 23 18:42:39 mother-base systemd[1]: nvidia-suspend.service: Deactivated successfully.
Oct 23 18:42:39 mother-base systemd[1]: Finished NVIDIA system suspend actions.
Oct 23 18:42:39 mother-base systemd[1]: Starting System Suspend...
Oct 23 18:42:39 mother-base systemd-sleep[29039]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Oct 23 18:42:39 mother-base systemd-sleep[29039]: This is not recommended, and might result in unexpected behavior, particularly
Oct 23 18:42:39 mother-base systemd-sleep[29039]: in suspend-then-hibernate operations or setups with encrypted home directories.
Oct 23 18:42:39 mother-base systemd-sleep[29039]: Performing sleep operation 'suspend'...
Oct 23 18:42:39 mother-base kernel: PM: suspend entry (deep)

Lotus · 2024-10-25 11:35:29

Same issue here, system specs:

B760M aorus elite AX motherboard
i5-13600KF CPU
Kingston KC3000 nvme 
AMD 6700 XT GPU

Current kernel version is 6.11.5 but I already tried switching to linux-lts with no success. I also have an additional buggy behavior, when trying to enter sleep state everything goes blank, but fans speed up and LEDs on the motherboard stay on.

Also I don't have a mediatek wireless card so the bluetooth solution is not working for me

Last edited by Lotus (2024-10-25 12:17:35)

seth · 2024-10-25 15:01:37

Also I don't have a mediatek wireless card so

*not*

Same issue here

=> Open a new thread and provide some data on the system, notably whether you can suspend from the multi-user.target, whether you can ssh into the system switch the VT or https://wiki.archlinux.org/title/Keyboa … el_(SysRq) and also whether and which was the last known good kernel.

nvme's are frequent subject to APST issues, so see https://wiki.archlinux.org/title/Solid_ … leshooting

Edit:

additional buggy behavior, when trying to enter sleep state everything goes blank, but fans speed up and LEDs on the motherboard stay on.

So you're not even entering the sleep state at all.

Add

cat /sys/power/mem_sleep
sudo journalctl -b | curl -F 'file=@-' 0x0.st

to your new thread.

Last edited by seth (2024-10-25 15:02:51)

Arch Linux

#51 2024-10-14 23:29:26

Re: Black screen after resuming from sleep

#52 2024-10-15 04:21:53

Re: Black screen after resuming from sleep

#53 2024-10-15 07:05:48

Re: Black screen after resuming from sleep

#54 2024-10-15 09:02:32

Re: Black screen after resuming from sleep

#55 2024-10-15 17:02:49

Re: Black screen after resuming from sleep

#56 2024-10-15 19:17:31

Re: Black screen after resuming from sleep

#57 2024-10-16 03:19:41

Re: Black screen after resuming from sleep

#58 2024-10-16 03:23:29

Re: Black screen after resuming from sleep

#59 2024-10-16 07:03:53

Re: Black screen after resuming from sleep

#60 2024-10-16 17:40:36

Re: Black screen after resuming from sleep

#61 2024-10-16 20:28:48

Re: Black screen after resuming from sleep

#62 2024-10-16 20:37:16

Re: Black screen after resuming from sleep

#63 2024-10-16 21:10:15

Re: Black screen after resuming from sleep

#64 2024-10-16 21:22:56

Re: Black screen after resuming from sleep

#65 2024-10-16 21:29:56

Re: Black screen after resuming from sleep

#66 2024-10-16 21:51:11

Re: Black screen after resuming from sleep

#67 2024-10-17 01:18:44

Re: Black screen after resuming from sleep

#68 2024-10-17 07:26:35

Re: Black screen after resuming from sleep

#69 2024-10-17 17:44:47

Re: Black screen after resuming from sleep

#70 2024-10-18 10:40:41

Re: Black screen after resuming from sleep

#71 2024-10-24 09:09:43

Re: Black screen after resuming from sleep

#72 2024-10-25 11:35:29

Re: Black screen after resuming from sleep

#73 2024-10-25 15:01:37

Re: Black screen after resuming from sleep

Board footer