Suspend issue with AMD Ryzen 8840U CPU and kernel 6.8.0-45-generic

[Dimitris Karagiannis]

I am running a new installation of Ubuntu noble 24.04 x86_64 (kernel 6.8.0-45-generic) on a brand new Thinkpad T14 Gen 5 (AMD Ryzen 7 PRO 8840U w/ Radeon 780M Graphics (16) @ 6.08 GHz)

The machine does not suspend properly, which I noticed after returning from work with it in my backpack, taking it out and it was hot.

While suspended the screen is in fact off, and the relevant LEDs enter a "breath" mode, indicating a suspended state, but there is an audible mechanical "tick" sound coming from the bottom, where I suppose the fan is located, and the laptop produces heat (gets hot if it's in a closed environment like my backpack)

At first I thought it was a "lid closed" issue, but after further experimentation turns out that it's not a lid issue, but rather a suspension issue; suspending from the power button has the same result

I could not reproduce this behaviour on Windows (I am dual booting, Windows Fastboot is off btw); suspending works properly; tested it, no "tick" sound, no heat.

P.S. for what it's worth, my Thinkpad x13 Gen 1 on ubuntu 22, same kernel version on AMD Ryzen Pro 7 4750U, has no issues with suspend.

Attaching system specs below. Please let me know what other info I need to provide

Thanks.
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-09-29 (3 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: LENOVO 21MCS06F00
Package: linux (not installed)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-45-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
RelatedPackageVersions:
 linux-restricted-modules-6.8.0-45-generic N/A
 linux-backports-modules-6.8.0-45-generic N/A
 linux-firmware 20240318.git3b128b60-0ubuntu2.4
Tags: noble wayland-session
Uname: Linux 6.8.0-45-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 08/07/2024
dmi.bios.release: 1.8
dmi.bios.vendor: LENOVO
dmi.bios.version: R2LET27W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21MCS06F00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnLENOVO:bvrR2LET27W(1.08):bd08/07/2024:br1.8:efr1.4:svnLENOVO:pn21MCS06F00:pvrThinkPadT14Gen5:rvnLENOVO:rn21MCS06F00:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21MC_BU_Think_FM_ThinkPadT14Gen5:
dmi.product.family: ThinkPad T14 Gen 5
dmi.product.name: 21MCS06F00
dmi.product.sku: LENOVO_MT_21MC_BU_Think_FM_ThinkPad T14 Gen 5
dmi.product.version: ThinkPad T14 Gen 5
dmi.sys.vendor: LENOVO

[Juerg Haefliger (juergh)]

Please run 'apport-collect 2083454` on that machine which will collect logs and attach them to this report.

[Dimitris Karagiannis (mkarajohn)]

Ok, now I am going to look really stupid now, but last night after reporting the issue here I got a Lenovo BIOS/UEFI firmware update notification for the laptop (was on 0.1.7 asking me to upgrade to 0.1.8).

I upgraded and retested. I retested it today for the duration of the day just to be sure and I can confirm that there is no longer an issue with firmware 0.1.8 thus far.

I know it looks silly, but I had seriously tested it, before there was an update, to make sure I do not open a rubbish report here; there was 100% an issue with suspend on 0.1.7 specifically on the Ubuntu installation. I will attach system logs as requested anyway, just in case there is something there that is of value.

Sorry for wasting your time if this proves to be a dud.

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Dimitris Karagiannis (mkarajohn)]

apport information

[Matthew Ruffell (mruffell)]

Hi Dimitris,

Don't worry, there is no such thing as silly questions. Someone out there will also have the same issue, eventually. Or it might randomly come back.

Maybe something to do with bug 2083453?

The clicking could be the ethernet device turning on and off?

If you look at journalctl -b0 or maybe -b-1 or maybe -b-2, find a boot where it failed to suspend. Is there any errors after PM: suspend entry (s2idle) in the logs? You can also look at /var/log/kern.log or /var/log/syslog.

Thanks,
Matthew