70-second black screen after waking from suspend

samesh77 · Yesterday 14:08:37

Hi,
I'm fairly new to Arch (about a month in), and I've run into an issue that started roughly a week ago.

Whenever I suspend my PC (system suspend) and wake it again, it takes about 70 seconds before my desktop appears.

During those ~70 seconds:
- both monitors wake up (backlight turns on)
- the screens stay black
- keyboard and mouse light up
- Caps Lock LED responds normally
- I can not open a TTY

This is my hardware:
- Motherboard: MSI MAG X870E TOMAHAWK MAX WIFI
- CPU: Ryzen 9 7900X
- GPU 1: Gigabyte RTX 5060 Ti 16GB
- GPU 2: Radeon RX 6600 8GB
- CPU Cooler: Deepcool LD360 ARGB
- RAM: 48GB DDR5 (2×24GB)

The monitors are connected to the RTX 5060 Ti

This is my software
- Arch Linux
- Kernel: 7.1.3-arch1-3
- Hyprland (latest, Lua config)
- SDDM

The RX 6600 is currently just installed in the system. My long-term plan is to use it for display output while using the RTX 5060 Ti for local LLMs/ML workloads, but I haven't configured anything like that yet.

This suspend issue did not happen until about a week ago.

Possibly related observations:

- During boot I consistently see:
usb 3-12: device descriptor read/64, error -110
and other errors (i have attached pictures)
I couldn't determine which USB device this corresponds to 3-12.

- Another odd observation:
When I disabled the Ryzen integrated graphics in BIOS and booted Arch:
- monitor layout reverted to defaults
- wallpaper disappeared
- Hyprland splash text reappeared
- however, all of my custom keybinds still worked
(i have attached pictures)
Re-enabling the iGPU restored everything to normal.
I'm not sure whether that's relevant or simply a side effect of changing GPUs.

Things I've tried:
- Disconnecting every USB device except keyboard and mouse.
The issue still occurs.

Complete logs are here:
https://gist.github.com/Samesh-Deshmukh … d10d49940d

Photos are here:
https://postimg.cc/gallery/vVTWdq4

Has anyone seen a long delay like this after resume? I'm not sure whether I should be looking at NVIDIA, Hyprland, systemd sleep, USB, firmware, or something else.

Last edited by samesh77 (Yesterday 14:09:29)

seth · Yesterday 14:49:39

Jul 21 13:21:37 SameshPCarch kernel: Linux version 7.1.3-arch1-3 (linux@archlinux) (gcc (GCC) 16.1.1 20260625, GNU ld (GNU Binutils) 2.46.1) #1 SMP PREEMPT_DYNAMIC Mon, 13 Jul 2026 20:15:15 +0000
Jul 21 13:21:41 SameshPCarch systemd-logind[712]: New session 'c1' of user 'sddm' with class 'greeter' and type 'x11'.
Jul 21 13:21:42 SameshPCarch systemd-logind[712]: New session '1' of user 'sddm' with class 'manager-early' and type 'unspecified'.
Jul 21 13:21:47 SameshPCarch systemd-logind[712]: New session '2' of user 'samesh' with class 'user' and type 'wayland'.
Jul 21 13:21:48 SameshPCarch systemd-logind[712]: New session '3' of user 'samesh' with class 'manager' and type 'unspecified'.

But from the dmesg

Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: new high-speed USB device number 5 using xhci_hcd
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: device descriptor read/64, error -110
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: device descriptor read/64, error -110
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: new high-speed USB device number 6 using xhci_hcd
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: device descriptor read/64, error -110
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: device descriptor read/64, error -110
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: new high-speed USB device number 7 using xhci_hcd
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: Device not responding to setup address.
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: Device not responding to setup address.
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: device not accepting address 7, error -71
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: new high-speed USB device number 8 using xhci_hcd
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: Device not responding to setup address.
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: Device not responding to setup address.
Jul 21 13:21:37 SameshPCarch kernel: usb 3-12: device not accepting address 8, error -71

seems relevant?

Same hub as

Jul 21 13:21:37 SameshPCarch kernel: usb 3-1: Product: G502 HERO Gaming Mouse
Jul 21 13:21:37 SameshPCarch kernel: usb 3-1: Manufacturer: Logitech
…
Jul 21 13:21:37 SameshPCarch kernel: usb 3-3: Product: Gaming KB 
Jul 21 13:21:37 SameshPCarch kernel: usb 3-3: Manufacturer: SINO WEALTH
…
Jul 21 13:21:37 SameshPCarch kernel: usb 3-11: Product: MYSTIC LIGHT
Jul 21 13:21:37 SameshPCarch kernel: usb 3-11: Manufacturer: MSI

Since the device never responds there's no direct way of telling what it is.

- Disconnecting every USB device except keyboard and mouse.
The issue still occurs.

Does the usb error remain?
Did you also unplug the onboard devices?
Can you disable bluetooth or webcam in the UEFI?
Do you have a $5 office-supply mouse/keyboard?

Edit: fuck.

Whenever I suspend my PC (system suspend) and wake it again, it takes about 70 seconds before my desktop appears.

The journal in the gist doesn't even cover that.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

*after* a slow wakeup from sleep.

Last edited by seth (Yesterday 14:52:55)

samesh77 · Yesterday 18:41:04

Does the usb error remain?

yes - thats what i meant

Did you also unplug the onboard devices?

the first time i only unplugged the usb devices connecting to the back of the motherboard(except the keyboard and mouse), but i tested a second time, this time removing every usb device connecting to the back of the motherboard(this time including the keyboard and mouse) and every usb device connecting to the motherboard pins, but weirdly the error still persisted

Do you have a $5 office-supply mouse/keyboard?

yeah i got

Please post your complete system journal for the boot:

https://paste.c-net.org/MemphisDesires
i also added it to the gist

seth · Yesterday 19:23:55

Jul 21 23:50:27 SameshPCarch kernel: ntfs3: Enabled Linux POSIX ACLs support
Jul 21 23:50:27 SameshPCarch kernel: ntfs3: Read-only LZX/Xpress compression included

There're two nvme's and two sata devices - are there other OS (notably windows) installed?

Jul 22 00:03:19 SameshPCarch systemd[1]: Starting NVIDIA system resume actions...
Jul 22 00:03:19 SameshPCarch systemd[1]: Stopped target Suspend.
Jul 22 00:03:19 SameshPCarch systemd-logind[740]: Operation 'suspend' finished.
Jul 22 00:03:19 SameshPCarch NetworkManager[737]: <info>  [1784658799.9349] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jul 22 00:03:19 SameshPCarch NetworkManager[737]: <info>  [1784658799.9349] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jul 22 00:03:19 SameshPCarch suspend[9935]: nvidia-resume.service
Jul 22 00:03:19 SameshPCarch logger[9935]: <13>Jul 22 00:03:19 suspend: nvidia-resume.service
Jul 22 00:03:19 SameshPCarch systemd[1]: nvidia-resume.service: Deactivated successfully.
…
Jul 22 00:04:10 SameshPCarch kernel: usb 3-12: Device not responding to setup address.
Jul 22 00:04:10 SameshPCarch kernel: usb 3-12: device not accepting address 11, error -71
Jul 22 00:04:10 SameshPCarch kernel: usb 3-12: new high-speed USB device number 12 using xhci_hcd
Jul 22 00:04:15 SameshPCarch kernel: usb 3-12: Device not responding to setup address.
Jul 22 00:04:17 SameshPCarch systemd-udevd[516]: 3-3: Worker [9890] processing SEQNUM=7257 is taking a long time.
Jul 22 00:04:17 SameshPCarch systemd-udevd[516]: 3-1: Worker [9925] processing SEQNUM=7260 is taking a long time.
Jul 22 00:04:20 SameshPCarch systemd-udevd[516]: 3-11: Worker [9921] processing SEQNUM=7307 is taking a long time.

Jul 21 23:50:25 SameshPCarch kernel: DMI: Micro-Star International Co., Ltd. MS-7E59/MAG X870E TOMAHAWK MAX WIFI (MS-7E59), BIOS 5.A32 06/25/2026

That thing is supposed to have a bluetooth chip, but neither wifi nor bluetooth seem to exist?

Just ftr there're also three VGA devices

Jul 21 23:50:27 SameshPCarch kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga console
Jul 22 00:03:16 SameshPCarch kernel: amdgpu 0000:7b:00.0: [drm] Cannot find any crtc or sizes
Jul 22 00:03:16 SameshPCarch kernel: amdgpu 0000:12:00.0: [drm] Cannot find any crtc or sizes

samesh77 · Today 05:49:38

are there other OS (notably windows) installed?

Yeah, i got windows installed on the 500gb nvme drive.
i got a 1tb nvme, 500gb nvme, 4tb hdd, 500gb sata ssd

That thing is supposed to have a bluetooth chip, but neither wifi nor bluetooth seem to exist?

you mean the motherboard? i comes with a bluetooth/wifi antenna, but i dont really use it cuz i have ethernet.
Though not sure if this is related, but i have been able to connect my wireless headphones to the pc in the past, but recently i havent. i didnt go deep into troubleshooting this error, so not sure of the cause.

Jul 21 23:50:27 SameshPCarch kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga console
Jul 22 00:03:16 SameshPCarch kernel: amdgpu 0000:7b:00.0: [drm] Cannot find any crtc or sizes
Jul 22 00:03:16 SameshPCarch kernel: amdgpu 0000:12:00.0: [drm] Cannot find any crtc or sizes

i think these errors are expected because my monitors are only plugged into the nvidia gpu. so both amd gpus are headless.

seth · Today 05:54:30

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

See whether radio works on windows resp isn't disabled in the UEFI settings.

samesh77 · Today 07:54:34

I have already fast startup disabled

C:\Windows\System32>powercfg /a
The following sleep states are available on this system:
Standby (S3)
The following sleep states are not available on this system:
Standby (S1)
The system firmware does not support this standby state.
Standby (S2)
The system firmware does not support this standby state.
Hibernate
Hibernation has not been enabled.
Standby (S0 Low Power Idle)
The system firmware does not support this standby state.
Hybrid Sleep
Hibernation is not available.
The hypervisor does not support this standby state.
Fast Startup
Hibernation is not available.

C:\Windows\System32>

Also, when i booted into windows, i got a similar usb error.
Wifi works on windows but bluetooth does not. I checked in Windows Update and my system is up to date.
i put some photos on: https://postimg.cc/gallery/vG7xV0t edit: changed the url to include some more images

Last edited by samesh77 (Today 08:01:01)

seth · Today 12:09:33

=> Can you disable BT in the UEFI settings?

samesh77 · Today 13:50:06

i can disable onboard wifi and bluetooth in uefi settings, but i am not sure if it is the same as the antenna connected to the motherboard. It is currently set to auto, should i change it?

seth · Today 14:18:33

Yes, the antenna doesn't matter so much - the question is whether BT is the misbehaving USB device.
W/ a little luck, turning it off and on again also repairs it

samesh77 · Today 15:00:37

So I changed the setting to Wi-Fi and Bluetooth off, and the USB error disappeared. However, when I tried suspending and waking the system, the screen stayed black (same as before), i waited around 2 minutes. I thought it might just be a graphical issue, so I pressed Super + T to open a terminal and then typed reboot, which worked. I repeated this twice, so it doesn't seem like a one-off.

Next, I changed the setting to Wi-Fi only. The USB error still didn't appear, and this time suspend/resume worked normally. I'm currently using this setting.

After that, I changed the setting back to Auto (I skipped `Bluetooth only` since I figured Bluetooth was likely problem). Initially, the USB error was still gone, but when I suspended and resumed, I got the following error:

[ 35.146801] Bluetooth: hci0: Failed to load firmware file (-2)
[ 35.146801] Bluetooth: hci0: Failed to set up firmware (-2)

After rebooting, the USB error returned, and the suspend/resume cycle once again took around 70 seconds, just like before.

Last edited by samesh77 (Today 15:02:08)

Arch Linux

#1 Yesterday 14:08:37

70-second black screen after waking from suspend

#2 Yesterday 14:49:39

Re: 70-second black screen after waking from suspend

#3 Yesterday 18:41:04

Re: 70-second black screen after waking from suspend

#4 Yesterday 19:23:55

Re: 70-second black screen after waking from suspend

#5 Today 05:49:38

Re: 70-second black screen after waking from suspend

#6 Today 05:54:30

Re: 70-second black screen after waking from suspend

#7 Today 07:54:34

Re: 70-second black screen after waking from suspend

#8 Today 12:09:33

Re: 70-second black screen after waking from suspend

#9 Today 13:50:06

Re: 70-second black screen after waking from suspend

#10 Today 14:18:33

Re: 70-second black screen after waking from suspend

#11 Today 15:00:37

Re: 70-second black screen after waking from suspend

Board footer