Laptop, sometimes, freeze on resume

The laptop used to resume correctly until about a month ago. Since then, sometimes, it freezes on resume.

Setup:

  • Laptop Model: Lenovo ThinkPad P52
  • Processor: 8th Generation Intel® Core™ i7-8750H Processor (2.20 GHz, up to 4.10 GHz with Turbo Boost, 6 Cores, 12 Threads, 9 MB Cache)
  • Display Type: 15.6" FHD (1920 x 1080) IPS, anti-glare, 300 nits
  • Memory: 32 GB DDR4 2400MHz (2 x 16 GB)
  • Hard Drive: 1 TB PCIe SSD
  • Graphics: NVIDIA® Quadro® P1000 4GB GDDR5
  • Keyboard: Backlit with Number Pad - US English
  • Battery: 6 Cell Li-Ion 90Wh
  • Camera: 720p HD
  • Fingerprint Reader: Fingerprint Reader
  • Wireless: Intel® 9560 802.11AC (2 x 2) & Bluetooth® 5.0
  • Operating System: Qubes OS 4.2.4
  • [dom0] uname -a: Linux dom0 6.12.39-1.qubes.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Jul 22 05:09:16 GMT 2025 x86_64 x86_64 x86_64 GNU/Linux
  • Screen lock: i3lock

Here is the sequence of events:

  • The system is sleeping. The power button LED blinks slowly.
  • I press the power button
  • The power button LED stops blinking and stays on.

a) Here is what happens after when it resumes correctly:

  • The wifi LED turns on
  • The disk usage LED starts blinking
  • The lock screen wallpaper shows up
  • I can enter my password

b) Here is what happens after when it does not resume correctly:

  • The wifi LED stays off
  • The disk usage LED stays off
  • The screen stays black
  • I cannot enter my password
  • Pressing Ctrl+Alt+F<number> does not change TTY
  • Pressing NumLock does not change the NumLock LED
  • Pressing Fn+FnLock does change the FnLock LED
  • I have to press the Power button for several seconds to reset.

Questions:

  • What could be the cause of this issue?
  • I have no idea of what could cause this problem. What should I do to gain more insight about this problem?
  • How do I fix this problem?

I have (had) the same issue at i5-8250 processor.

Now, at R4.3 not sure fixed or not.

this is bug after xen security update

more info:

2 Likes

I have the same issue.

When is this going to be fixed?

Maybe in 4.3 because there will be newest MESA dri drivers…

The solution in this GitHub worked for me. I’ve been testing this for the past 7 days.

I ran this from Dom0 to resolve my issue:

# Check and note the current Release and Source
sudo dnf info xen-hypervisor

# Upgraded to xen-hypervisor-4.17.5-11.118.fc37 via this command
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable --action=update xen-hypervisor

# Check and confirm upgraded Release and Source
sudo dnf info xen-hypervisor

# profit