I've tried to get my hands a bit dirty on this bug to be more helpful than
just forwarding messages to Intel and back.
So, I've selected two Intel Xeon Sapphire Rapids (SPR) machines[1][2] to
perform tests and with the results I don't feel confident that we can 100%
blame intel-microcode just yet. With one of the machines[2] on jammy and
with latest microcode and hwe-6.8 kernel the issue doesn't reproduce. And
also, given that with kernel 5.15 and latest microcode the issue doesn't
happen could be seen as another clue that maybe we are dealing with a bug
in a different place. One thing that I tried when chasing for machines was
to try different GPU configurations, could it be related somehow? One has
a nvidia GPU[1] while the other doesn't[2].

Kevin, do you have access to these machines, or similar configurations
variations, and could try to help us out with your tests?

Below are my simplistic test routine in details:
1. Initial state
machine[1]:
   ubuntu@hidon:~$ uname -a
   Linux hidon 5.15.0-151-generic #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025 
x86_64 x86_64 x86_64 GNU/Linux
   ubuntu@hidon:~$ apt-cache policy intel-microcode
   intel-microcode:
   Installed: 3.20250512.0ubuntu0.22.04.1
   Candidate: 3.20250512.0ubuntu0.22.04.1
   Version table:
   *** 3.20250512.0ubuntu0.22.04.1 500
         500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
         500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
         100 /var/lib/dpkg/status
      3.20210608.2ubuntu1 500
         500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

machine[2]:
   ubuntu@smilax:~$ uname -a
   Linux smilax 5.15.0-151-generic #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025 
x86_64 x86_64 x86_64 GNU/Linux
   ubuntu@smilax:~$ apt-cache policy intel-microcode
   intel-microcode:
   Installed: 3.20250512.0ubuntu0.22.04.1
   Candidate: 3.20250512.0ubuntu0.22.04.1
   Version table:
   *** 3.20250512.0ubuntu0.22.04.1 500
         500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
         500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
         100 /var/lib/dpkg/status
      3.20210608.2ubuntu1 500
         500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

2. $ sudo rtcwake -m no -s 60;sudo systemctl suspend
   * machine[1] and machine[2]: system came back after ~60 secs.
3. $ sudo apt install linux-generic-hwe-22.04 #-> upgrade the kernel to 
6.8.0-65.68~22.04.1
4. $ sudo reboot
5. $ sudo rtcwake -m no -s 60;sudo systemctl suspend
   * machine[1]: system got stuck
   * machine[2]: system came back after ~60 secs.

Beside the simplistic tests, I have tried noble on machine[1] and
downgraded the microcode version and the issue was still reproducible,
which was quite interesting:
   $ uname -a
   Linux hidon 6.8.0-71-generic #71-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 22 
16:52:38 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
   $ sudo apt install intel-microcode=3.20240312.1build1
   ubuntu@hidon:~$ apt-cache policy intel-microcode
   intel-microcode:
     Installed: 3.20240312.1build1
     Candidate: 3.20250512.0ubuntu0.24.04.1
     Version table:
        3.20250512.0ubuntu0.24.04.1 500
           500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
Packages
           500 http://archive.ubuntu.com/ubuntu noble-security/main amd64 
Packages
    *** 3.20240312.1build1 500
           500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
           100 /var/lib/dpkg/status
   $ sudo reboot
   $ sudo rtcwake -m no -s 60;sudo systemctl suspend
   * system got stuck

[1] https://certification.canonical.com/hardware/202311-32290/
[2] https://certification.canonical.com/hardware/202310-32219/

** Changed in: intel-microcode (Ubuntu)
       Status: New => Incomplete

** Changed in: intel-microcode (Ubuntu)
     Assignee: (unassigned) => Rodrigo Figueiredo Zaiden (rodrigo-zaiden)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2115854

Title:
  The system didn’t go into suspend and got stuck

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/2115854/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to