6.2 kernel on Ubuntu 22.04 causes wake from suspend failures on MacBook Pro (Retina, 13-inch, Early 2015) Model Identifier: MacBookPro12,1

[Steven Freeman]

Disabling Wayland partially helps but eventually will cause the computer to not wake up. This occurs both when closing the lid and when leaving the computer idle for some time.

Description: Ubuntu 22.04.3 LTS
Release: 22.04

intel-microcode:
  Installed: 3.20230808.0ubuntu0.22.04.1

I expected resume from sleep/suspend to behave as it did prior. If I would open the lid or push any keys, the computer would wake up from sleep/suspend.

Instead, the computer does not wake from sleep/suspend and I need to force the computer to shutdown using the power button and then turn it back on again.

[Mark Esler (eslerm)]

Could you please confirm this bug by disabling the microcode with the dis_ucode_ldr kernel parameter and retesting sleep/suspend?

If you can verify that Intel Microcode 06-a7-01 disrupts sleep/suspend, please also file an issue with https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files

[Steven Freeman (jrjrjr422)]

I added GRUB_CMDLINE_LINUX_DEFAULT="dis_ucode_ldr" and rebooted and suspend still was broken. Seems like intel-microcode was perhaps a red herring. Wondering what I can do to further debug this since the problem seemed to arise after an apt update && apt upgrade but I am not sure what may have broken suspend/sleep. Perhaps the update && upgrade is a red herring as well and merely coincidental since as I said, the other packages that were updated would seemingly have no effect on this behavior...

[Steven Freeman (jrjrjr422)]

I also just now downgraded intel-microcode to the version I had prior to the update to no avail. So I think its safe to say it has nothing to do with intel-microcode. Changed title to reflect

[Steven Freeman (jrjrjr422)]

This is unrelated to intel-microcode.

[Steven Freeman (jrjrjr422)]

To help debug, this is the result of cat /var/log/apt/history.log from when I began noticing the problem til today:

Start-Date: 2023-08-14 13:58:38
Commandline: apt upgrade -y
Requested-By: steve (1000)
Upgrade: libldap-common:amd64 (2.5.15+dfsg-0ubuntu0.22.04.1, 2.5.16+dfsg-0ubuntu0.22.04.1), libldap-2.5-0:amd64 (2.5.15+dfsg-0ubuntu0.22.04.1, 2.5.16+dfsg-0ubuntu0.22.04.1), code:amd64 (1.81.0-1690980880, 1.81.1-1691620686), intel-microcode:amd64 (3.20230214.0ubuntu0.22.04.1, 3.20230808.0ubuntu0.22.04.1), linux-libc-dev:amd64 (5.15.0-78.85, 5.15.0-79.86)
End-Date: 2023-08-14 13:59:23

Start-Date: 2023-08-14 16:07:36
Commandline: apt upgrade -y
Requested-By: steve (1000)
Upgrade: insomnia:amd64 (2023.3.0, 2023.5.0)
End-Date: 2023-08-14 16:07:53

Start-Date: 2023-08-15 18:28:19
Commandline: aptdaemon role='role-commit-packages' sender=':1.122'
Upgrade: redis-server:amd64 (6:7.0.12-1rl1~jammy1, 6:7.2.0-1rl1~jammy1), insomnia:amd64 (2023.5.0, 2023.5.2), mysql-server-8.0:amd64 (8.0.33-0ubuntu0.22.04.4, 8.0.34-0ubuntu0.22.04.1), mysql-client-8.0:amd64 (8.0.33-0ubuntu0.22.04.4, 8.0.34-0ubuntu0.22.04.1), libtiff5:amd64 (4.3.0-6ubuntu0.4, 4.3.0-6ubuntu0.5), gir1.2-javascriptcoregtk-4.0:amd64 (2.40.4-0ubuntu0.22.04.1, 2.40.5-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.40.4-0ubuntu0.22.04.1, 2.40.5-0ubuntu0.22.04.1), redis-tools:amd64 (6:7.0.12-1rl1~jammy1, 6:7.2.0-1rl1~jammy1), libjavascriptcoregtk-4.0-18:amd64 (2.40.4-0ubuntu0.22.04.1, 2.40.5-0ubuntu0.22.04.1), mysql-server:amd64 (8.0.33-0ubuntu0.22.04.4, 8.0.34-0ubuntu0.22.04.1), mysql-server-core-8.0:amd64 (8.0.33-0ubuntu0.22.04.4, 8.0.34-0ubuntu0.22.04.1), libwebkit2gtk-4.0-37:amd64 (2.40.4-0ubuntu0.22.04.1, 2.40.5-0ubuntu0.22.04.1), mysql-client-core-8.0:amd64 (8.0.33-0ubuntu0.22.04.4, 8.0.34-0ubuntu0.22.04.1)
End-Date: 2023-08-15 18:29:17

Start-Date: 2023-08-16 11:44:54
Commandline: apt upgrade -y
Requested-By: steve (1000)
Upgrade: insomnia:amd64 (2023.5.2, 2023.5.3)
End-Date: 2023-08-16 11:45:11

Start-Date: 2023-08-17 17:06:30
Commandline: apt-get install git
Requested-By: steve (1000)
Upgrade: git:amd64 (1:2.34.1-1ubuntu1.9, 1:2.34.1-1ubuntu1.10)
End-Date: 2023-08-17 17:06:31

Start-Date: 2023-08-17 17:53:56
Commandline: apt remove intel-microcode
Requested-By: steve (1000)
Remove: linux-image-generic-hwe-22.04:amd64 (6.2.0.26.26~22.04.7), linux-generic-hwe-22.04:amd64 (6.2.0.26.26~22.04.7), intel-microcode:amd64 (3.20230808.0ubuntu0.22.04.1)
End-Date: 2023-08-17 17:54:09

Start-Date: 2023-08-17 17:54:14
Commandline: apt install intel-microcode=3.20210608.2ubuntu1
Requested-By: steve (1000)
Install: intel-microcode:amd64 (3.20210608.2ubuntu1)
End-Date: 2023-08-17 17:54:27

Start-Date: 2023-08-17 17:58:10
Commandline: apt upgrade -y
Requested-By: steve (1000)
Upgrade: ghostscript-x:amd64 (9.55.0~dfsg1-0ubuntu5.3, 9.55.0~dfsg1-0ubuntu5.4), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.2, 2:4.15.13+dfsg-0ubuntu1.3), libgs9-common:amd64 (9.55.0~dfsg1-0ubuntu5.3, 9.55.0~dfsg1-0ubuntu5.4), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.2, 2:4.15.13+dfsg-0ubuntu1.3), ghostscript:amd64 (9.55.0~dfsg1-0ubuntu5.3, 9.55.0~dfsg1-0ubuntu5.4), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.2, 2:4.1...

[Mark Esler (eslerm)]

Does the issue go away if you boot from the installer into the live Ubuntu demo? If not, I might try the live demo of an older release in case there was a regression afterwards.

[Steve Beattie (sbeattie)]

Hey Steve, sorry you're having issues.

One thing that would be useful to know is which kernel versions you're experiencing this under. I notice in the apt.log that when the newer version of the intel-microcode package was removed, apt also removed the meta packages for the linux-generic-hwe-22.04 kernel, which would not have uninstalled the current 6.2.0 linux kernel, but it *will prevent* apt from pulling future kernel updates for you, so you will want to reinstall the linux-generic-hwe-22.04 package.

One possible cause of this issue might be that the 22.04 kernel moved recently from being based on the upstream 5.19 kernel to the 6.2 kernel. If you still have 5.19 kernels installed, you might try rebooting into one of those and seeing if the waking from suspend issue is a problem there, too. To do that, you'll need to get into the grub menu on boot, and select an older kernel to boot into. You may need to modify in /etc/default/grub the GRUB_TIMEOUT_STYLE setting to menu and to set the GRUB_TIMEOUT value to a non-zero value, running sudo update-grub after making your edits.

[Steven Freeman (jrjrjr422)]

Thank you! I tried booting into the 5.19 kernel and so far, the issue seems to be resolved. I think you were spot on with the kernel recommendation Steve.

Given that I've only temporarily booted into this kernel via grub - is there a way for me to set my computer to default to this kernel, at least for now, and maybe I can come back to 6.2 at a later date? Or perhaps I can open a thread re: this issue on 6.2 to try and discover what is going on under the hood that is breaking this behavior?

[Steve Beattie (sbeattie)]

Hey Steven,

The downside to setting grub to boot into a specific kernel by default is that your system won't get future seurity updates until you remember to undo it (and when I've done this in the past, I forget about it easily). That said, you can do it by again editing the GRUB_DEFAULT entry in /etc/default/grub to something like:

  GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 5.19.0-50-generic"

assuming that you have the last 5.19 kernel update installed on your system. You can use 'uname -r' to see the version of the kernel you are currently running where wake from suspend is successful, and adjust the "5.19.0-50-generic" portiong of the entry to match.

Hopefully the kernel team will get a chance to look at this and get the issue resovled for 6.2 kernels. If they are able to prepare test kernels, it would be appreciated if you could give them a try.

Thanks again!

[Steven Freeman (jrjrjr422)]

Awesome thank you for the advice! Happy to help where I can. I also updated the title since I had my laptop model wrong.

[Juerg Haefliger (juergh)]

Can you test the kernel from jammy-proposed? linux-hwe-6.2 version 6.2.0-32.32~22.04.1.

https://wiki.ubuntu.com/Testing/EnableProposed

[Steven Freeman (jrjrjr422)]

I am on the jammy-proposed kernel now and the computer seems to wake from suspend correctly however, it does take some time, longer than the 5.19.0.50-generic kernel that I was using per Steve's suggestion.

[Steven Freeman (jrjrjr422)]

On further use, I am noticing a few issues with 6.2.0.32.32-22.04.1:
- Closing the lid does not suspend
- The computer actually is not waking from suspend due to mouse/keyboard input/lid opening, rather it is waking from suspend because I use Mullvad VPN and it seems to be connecting to the VPN after I suspend, which in turn wakes the computer up.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marco Chiappero (mchiappero)]

I am on Ubuntu 22.04.3 LTS, but tried the 6.2.0-34-generic kernel.

From then on the PC did not fully recover from S3, and by this I mean that while the screen stays black I can switch to a terminal with a Alt + F# combination and trigger a successful reboot. As far as I can see it's not an Ubuntu specific issue, there is clearly a regression in the upstream kernel, but it would great if we could narrow this down.

Of course, the problem disappears when reverting back to the 5.13.0-30-generic I was using before.

I will review the logs, but in the meantime I hope it helps.