Black screen after resume from sleep (intermittent issue)

Support and Help
,
1

Ubuntu Version:
24.04.2 LTS (Kernel Linux 6.11.0-25-generic)

Desktop Environment (if applicable):
GNOME 46

Problem Description:
I’m experiencing an intermittent issue where my Ubuntu system fails to properly resume from sleep. When I try to wake the laptop, a blue LED indicates that the system is no longer sleeping, but the screen stays completely black. No matter how long I wait or what keys I press, nothing happens. I’m forced to hold down the power button to shut it off.

I previously used Ubuntu 22.04 LTS, and the same problem occurred there, so it’s not specific to the current version I’m running.

Unfortunately, I don’t know where to look for logs that might help diagnose the issue. If anyone can point me in the right direction, I’d really appreciate it.

I’ve been ignoring this problem for a while, but it’s now becoming more serious — I’ve lost data a few times, and one of the hard drives in my machine has started showing signs of failure, which I suspect might be related to these repeated forced shutdowns.

Relevant System Information:
Laptop Acer Aspire A315-42G-R6FZ
32GB RAM + 250GB NVMe SSD (Ubuntu) + 1TB HDD
CPU AMD Ryzen 5 3500U (with Vega 8 Graphics)
GPU AMD Radeon 540X

Screenshots or Error Messages:

What I’ve Tried:

2

Welcome to Ubuntu Discourse :slight_smile:

You will need to wait for someone with more knowledge in this matter but…please do NOT do hard shutdowns. This will cause possible data and filesystem corruption.

Instead, do this:
Alt + SysRq (Print Screen key)
Then press, one at a time (with a few seconds between each):
R E I S U B
Release the keys and the computer will reboot.

Alternatively, to shut down completely you can do this:
Alt + SysRq (Print Screen key)
Then press the keys in this order, one at a time, waiting 1–2 seconds between each:
R E I S U O

Both methods will gracefully shut down processes, avoiding corruption or other issues.

2 Likes
3

Sounds like the first good place to start, can you replace the drive and see if that helps?

4

I removed it from my laptop recently due to this issue, but the problem persists.

5

I wish I had better info for you, but Users have reported issues with resuming from suspend on systems with AMD GPUs, including the Radeon 540X, on Ubuntu.

I have a nVidia gpu here and suffer the same if not worse black screen of death. I don’t suspend or sleep my system, I’ll just throw it in Lock Screen, till I return.

Do you have any special setting on /etc/default/grub?

This is a common grub setting nvme.noacpi=1 if you have that you might want to try to remove it, and update-grub and a reboot.

Also Please be sure your current on all firmware updates and Bios updates.

I have a AMD CPU/GPU, and even with no nVidia driver installed… still the Black screen from resume.

Current kernel for myself is Linux 6.14.0-15-generic

Specs:

lsmod | rg -ie 'amd'
amd_atl                69632  1
edac_mce_amd           28672  0
snd_sof_amd_acp70      16384  0
snd_sof_amd_acp63      16384  0
snd_sof_amd_vangogh    16384  0
snd_sof_amd_rembrandt    16384  0
snd_sof_amd_renoir     16384  0
snd_sof_amd_acp        65536  5 snd_sof_amd_acp70,snd_sof_amd_rembrandt,snd_sof_amd_vangogh,snd_sof_amd_acp63,snd_sof_amd_renoir
snd_sof_pci            24576  5 snd_sof_amd_acp70,snd_sof_amd_rembrandt,snd_sof_amd_vangogh,snd_sof_amd_acp63,snd_sof_amd_renoir
snd_sof_xtensa_dsp     12288  1 snd_sof_amd_acp
snd_sof               401408  2 snd_sof_amd_acp,snd_sof_pci
snd_soc_acpi_amd_match     8192  2 snd_sof_amd_acp63,snd_pci_ps
snd_amd_sdw_acpi       16384  2 snd_sof_amd_acp,snd_pci_ps
soundwire_amd          45056  2 snd_sof_amd_acp,snd_pci_ps
soundwire_generic_allocation    24576  1 soundwire_amd
soundwire_bus         126976  2 soundwire_generic_allocation,soundwire_amd
amdgpu              19763200  53
snd_soc_core          434176  2 snd_sof,soundwire_amd
kvm_amd               245760  0
kvm                  1429504  1 kvm_amd
amdxcp                 12288  1 amdgpu
snd_acp_config         24576  10 snd_rn_pci_acp3x,snd_sof_amd_acp70,snd_pci_acp6x,snd_pci_acp5x,snd_sof_amd_rembrandt,snd_sof_amd_vangogh,snd_sof_amd_acp63,snd_acp_pci,snd_pci_ps,snd_sof_amd_renoir
gpu_sched              61440  1 amdgpu
snd_soc_acpi           16384  3 snd_sof_amd_acp,snd_acp_config,snd_pci_ps
drm_panel_backlight_quirks    12288  1 amdgpu
drm_buddy              24576  1 amdgpu
drm_exec               12288  1 amdgpu
drm_suballoc_helper    16384  1 amdgpu
drm_display_helper    282624  1 amdgpu
snd_pcm               196608  14 snd_sof_amd_acp,snd_hda_codec_hdmi,snd_pci_acp6x,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_sof,snd_compress,snd_soc_core,snd_sof_utils,soundwire_amd,snd_hda_core,snd_pci_ps,snd_pcm_dmaengine
cec                    94208  2 drm_display_helper,amdgpu
i2c_algo_bit           20480  1 amdgpu
drm_ttm_helper         16384  2 amdgpu,nvidia_drm
ccp                   159744  1 kvm_amd
ttm                   118784  2 amdgpu,drm_ttm_helper
video                  77824  3 amdgpu,ideapad_laptop,nvidia_modeset

To save you time I have personally tried these kernel params:
Tried amdgpu.dc=0, amdgpu.reset_method=2, amdgpu.runpm=0, nomodeset, pcie_aspm=force, acpi_osi=Linux, acpi_osi=Windows kernel parameters

None of which had any effect on resume. :frowning:

The Bug Team has many reports on this issue with all kinds of suggestions, but again nothing I find as a solution.

2 Likes
6

I had this problem as well with a previous kernel. My system would not output anything on screen after suspend. A workaround that worked for me was by dropping to a TTY, then ‘systemctl supend’.

Afterwards I did manage to get an error message on screen saying ‘Bluetooth: hci0: Failed to claim iso interface’. Disabling bluetooth and then suspending from GUI, did work for me.

But this was like 1-2 months ago and has been solved in my case with a newer kernel. I have an AMD GPU as well.

1 Like
7

@1fallen thanks for the suggestions. I usually carry my laptop in my backpack for work or school, so in those situations, just locking the screen isn’t an option because the fan keeps running. I don’t shut it down for convenience. Even with an NVMe SSD, having to boot up and reopen all my apps every time I take the laptop out of the backpack feels like wasted time.

I don’t have any special settings in /etc/default/grub, and my BIOS is up to date. I’ve already tried some of the parameters mentioned, but didn’t see any improvement.

This week, I disabled (unbind) the GPU (Radeon 540X) via systemd, but the issue is still there. The logs show some messages related to power controllers, so maybe some hardware isn’t resuming properly from suspend and is blocking the wake-up.

Today, I decided to keep the Radeon 540X unbound (I found out through glmark2 that the Vega 8 actually performs better) and also unbind the SATA controller (AHCI). I’ll check back next week with an update.

Below is the dmesg output from a failed attempt to enter suspend mode, where the screen turned off but the laptop froze while staying on. Strangely, the freeze stopped only after I pressed the power button long enough to almost shut down the laptop.

[Sun May 25 12:43:41 2025] wlp4s0: deauthenticating from f4:1f:c2:09:1d:ff by local choice (Reason: 3=DEAUTH_LEAVING)
[Sun May 25 12:43:42 2025] PM: suspend entry (s2idle)
[Sun May 25 12:43:42 2025] Filesystems sync: 0.015 seconds
[Sun May 25 12:43:42 2025] Freezing user space processes
[Sun May 25 12:43:42 2025] Freezing user space processes completed (elapsed 0.005 seconds)
[Sun May 25 12:43:42 2025] OOM killer disabled.
[Sun May 25 12:43:42 2025] Freezing remaining freezable tasks
[Sun May 25 12:43:42 2025] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[Sun May 25 12:43:42 2025] printk: Suspending console(s) (use no_console_suspend to debug)
[Sun May 25 12:43:42 2025] amdgpu 0000:05:00.0: amdgpu: Power consumption will be higher as BIOS has not been configured for suspend-to-idle.
                           To use suspend-to-idle change the sleep mode in BIOS setup.
[Sun May 25 12:43:42 2025] ACPI: EC: interrupt blocked
[Sun May 25 12:43:43 2025] ACPI: EC: interrupt unblocked
[Sun May 25 12:43:43 2025] acer_wmi: Unknown function number - 4 - 0
[Sun May 25 12:43:43 2025] acer_wmi: Unknown function number - 4 - 0
[Sun May 25 12:43:43 2025] acer_wmi: Unknown function number - 4 - 0
[Sun May 25 12:43:43 2025] acer_wmi: Unknown function number - 4 - 0
[Sun May 25 12:43:43 2025] atkbd serio0: Unknown key pressed (translated set 2, code 0x5b on isa0060/serio0).
[Sun May 25 12:43:43 2025] atkbd serio0: Use 'setkeycodes 5b <keycode>' to make it known.
[Sun May 25 12:43:43 2025] acer_wmi: Unknown function number - 4 - 0
[Sun May 25 12:43:43 2025] acer_wmi: Unknown function number - 4 - 0
[Sun May 25 12:43:43 2025] r8169 0000:03:00.0 enp3s0: Link is Down
[Sun May 25 12:43:43 2025] usb 1-1: reset high-speed USB device number 2 using xhci_hcd
[Sun May 25 12:43:44 2025] ahci 0000:06:00.0: Controller reset failed (0xffffffff)
[Sun May 25 12:43:44 2025] ahci 0000:06:00.0: PM: dpm_run_callback(): pci_pm_resume returns -5
[Sun May 25 12:43:44 2025] ahci 0000:06:00.0: PM: failed to resume async: error -5
[Sun May 25 12:43:44 2025] ahci 0000:06:00.0: AHCI controller unavailable!
[Sun May 25 12:43:44 2025] ahci 0000:06:00.0: AHCI controller unavailable!
[Sun May 25 12:43:44 2025] OOM killer enabled.
[Sun May 25 12:43:44 2025] Restarting tasks ... done.
[Sun May 25 12:43:44 2025] random: crng reseeded on system resumption
[Sun May 25 12:43:44 2025] PM: suspend exit
[Sun May 25 12:43:44 2025] Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
[Sun May 25 12:43:44 2025] r8169 0000:03:00.0 enp3s0: Link is Down
[Sun May 25 12:43:45 2025] ata1: failed to resume link (SControl FFFFFFFF)
[Sun May 25 12:43:45 2025] ata1: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)
[Sun May 25 12:43:45 2025] ahci 0000:06:00.0: AHCI controller unavailable!
[Sun May 25 12:43:49 2025] wlp4s0: VHT information is missing, disabling VHT
[Sun May 25 12:43:49 2025] wlp4s0: authenticate with f4:1f:c2:09:1d:ff (local address=a4:63:a1:29:7c:99)
[Sun May 25 12:43:49 2025] wlp4s0: send auth to f4:1f:c2:09:1d:ff (try 1/3)
[Sun May 25 12:43:49 2025] wlp4s0: authenticated
[Sun May 25 12:43:49 2025] wlp4s0: associate with f4:1f:c2:09:1d:ff (try 1/3)
[Sun May 25 12:43:49 2025] wlp4s0: RX AssocResp from f4:1f:c2:09:1d:ff (capab=0x1111 status=0 aid=11)
[Sun May 25 12:43:49 2025] wlp4s0: associated
[Sun May 25 12:43:49 2025] ath: EEPROM regdomain: 0x8114
[Sun May 25 12:43:49 2025] ath: EEPROM indicates we should expect a country code
[Sun May 25 12:43:49 2025] ath: doing EEPROM country->regdmn map search
[Sun May 25 12:43:49 2025] ath: country maps to regdmn code: 0x37
[Sun May 25 12:43:49 2025] ath: Country alpha2 being used: DE
[Sun May 25 12:43:49 2025] ath: Regpair used: 0x37
[Sun May 25 12:43:49 2025] ath: regdomain 0x8114 dynamically updated by country element
[Sun May 25 12:43:49 2025] wlp4s0: Limiting TX power to 17 dBm as advertised by f4:1f:c2:09:1d:ff
[Sun May 25 12:43:56 2025] audit: type=1400 audit(1748169836.094:845): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=361977 comm="hyper" requested="userns_create" target="unprivileged_userns"
[Sun May 25 12:43:56 2025] audit: type=1400 audit(1748169836.096:846): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=361979 comm="hyper" capability=21  capname="sys_admin"
[Sun May 25 12:46:35 2025] input: LIFT Mouse as /devices/virtual/misc/uhid/0005:046D:B031.0005/input/input28
[Sun May 25 12:46:35 2025] hid-generic 0005:046D:B031.0005: input,hidraw1: BLUETOOTH HID v0.11 Mouse [LIFT] on a4:63:a1:29:7c:9a
8

@gokhan61 I just noticed that after the failed suspend attempt I mentioned earlier, the Bluetooth turned off and I haven’t been able to turn it back on since (probably only after rebooting the system). That’s strange and curious.

bluetoothctl 
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# power on
No default controller available
9

That looks unusual to me, I block mine from auto start:

systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-05-25 08:05:38 MDT; 9min ago
 Invocation: bf1c1109af4449b3bc2c2676a31f7b97
       Docs: man:bluetoothd(8)
   Main PID: 2244 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 16288)
     Memory: 2.2M (peak: 2.7M)
        CPU: 130ms
     CGroup: /system.slice/bluetooth.service
             └─2244 /usr/libexec/bluetooth/bluetoothd

May 25 08:05:50 me-Legion-5-plasma-zfs bluetoothd[2244]: Endpoint registered: sender=:1.56 path=/MediaEndpoin>
May 25 08:05:50 me-Legion-5-plasma-zfs bluetoothd[2244]: Endpoint registered: sender=:1.56 path=/MediaEndpoin>
May 25 08:05:50 me-Legion-5-plasma-zfs bluetoothd[2244]: Endpoint registered: sender=:1.56 path=/MediaEndpoin>
May 25 08:05:50 me-Legion-5-plasma-zfs bluetoothd[2244]: Endpoint registered: sender=:1.56 path=/MediaEndpoin>
May 25 08:05:50 me-Legion-5-plasma-zfs bluetoothd[2244]: Endpoint registered: sender=:1.56 path=/MediaEndpoin>
May 25 08:05:50 me-Legion-5-plasma-zfs bluetoothd[2244]: Endpoint registered: sender=:1.56 path=/MediaEndpoin>
May 25 08:05:52 me-Legion-5-plasma-zfs bluetoothd[2244]: Failed to set mode: Failed (0x03)
May 25 08:05:52 me-Legion-5-plasma-zfs bluetoothd[2244]: Failed to set mode: Failed (0x03)
May 25 08:05:53 me-Legion-5-plasma-zfs bluetoothd[2244]: Failed to set mode: Failed (0x03)
lines 1-22


 bluetoothctl
Agent registered
[bluetoothctl]> show
Controller E0:0A:F6:81:81:92 (public)
        Manufacturer: 0x005d (93)
        Version: 0x0b (11)
        Name: me-Legion-5-plasma-zfs #1
        Alias: me-Legion-5-plasma-zfs #1
        Class: 0x00000000 (0)
        Powered: no
        PowerState: off-blocked
        Discoverable: no
        DiscoverableTimeout: 0x000000b4 (180)
        Pairable: yes
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: SIM Access                (0000112d-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Client   (0000112e-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0552
        Discovering: no
        Roles: central
        Roles: peripheral
Advertising Features:
        ActiveInstances: 0x00 (0)
        SupportedInstances: 0x0a (10)
        SupportedIncludes: tx-power
        SupportedIncludes: appearance
        SupportedIncludes: local-name
        SupportedSecondaryChannels: 1M
        SupportedSecondaryChannels: 2M
        SupportedSecondaryChannels: Coded
        SupportedCapabilities.MinTxPower: 0xfffffff0 (-16)
        SupportedCapabilities.MaxTxPower: 0x000a (10)
        SupportedCapabilities.MaxAdvLen: 0xfb (251)
        SupportedCapabilities.MaxScnRspLen: 0xfb (251)
        SupportedFeatures: CanSetTxPower
        SupportedFeatures: HardwareOffload
[bluetoothctl]>

Bluez is not the most reliable feature we have…lol

└─> bluetoothctl power on
Failed to set power on: org.bluez.Error.Failed
┌───────────────────>
│~ 
└─> sudo rfkill unblock bluetooth
┌───────────────────>
│~ 
└─> bluetoothctl power on
Changing power on succeeded

Regretfully I still have nothing for your suspend issue.

10

I once had a problem with bluetooth, and used this:

tim@black:/usr/lib/systemd/system-sleep$ more disable_bluetooth_power_fix.sh 
#!/bin/sh

if [ "${1}" == "pre" ]; then
    if [ -n "$(rfkill list bluetooth|grep 'Soft blocked: no')" ]; then
        touch /tmp/bluetooth-was-enabled-before-suspend
        rfkill block bluetooth
    fi
elif [ "${1}" == "post" ]; then
    if [ -f "/tmp/bluetooth-was-enabled-before-suspend" ]; then
        rfkill unblock bluetooth
        rm -f /tmp/bluetooth-was-enabled-before-suspend
    fi
fi

this was an an amd graphics card, but the problem came and went with a specific kernel a few months ago (24.04) and I’m not sure that it really was a bluetooth device problem.

11

I do not know if this will change anything on your issue but you may want to take a look at bios settings.

Searching pci_pm_resume points to PCI Power Management. Again you may start looking at bios and check settings there.

12

This might be a stupid suggestion - but it did help me solve a similar issue in the past.

Do you have control over the screen brightness? I.e. keys in the range F1-F12 which have additional functionality when pressed with the Fn (function) key?

I remember that sometime ago my laptop used to wake up with screen brightness turned all the way down.

The annoying bit is that it was also waking up to a screensaver in locked state which prevented the function keys to work.

So after I realized what was going on - I blindly typed in my password, pressed enter, and when the screensaver stopped, I was able to use the function keys to increase the brightness to full and see the desktop again.

Maybe this is not the issue you are facing, but can’t hurt to try?

Best of luck,
Valera Rozuvan

13

This topic was automatically closed after 30 days. New replies are no longer allowed.