I am the new owner of a Lenovo ThinkPad T14 gen 4 AMD.

I am seeing an issue on Linux where the system is soft rebooting when resuming from suspend.

I've put about 20 hours into this at this point, trying various combinations of software with the hope that I would find any combination that "just works", and I wouldn't have to really dig in on this issue...

But, It's clear to me now that if I am going make any progress, I have to Just start meticulously documenting test cases in the hopes that eventually I spot a pattern.

So, that's what I'll do.

In wrap up this post with a rough outline of my hardware configuration, since it shouldn't change during most of the testing that follow. And in subsequent posts I'll outline specific test cases.

ThinkPad T14 Gen 4 AMD Configuration

Processor AMD Ryzen™ 7 PRO 7840U Processor (3.30 GHz up to 5.10 GHz) selected upgrade
Operating System Windows 11 Pro 64 selected upgrade
Operating System Language Windows 11 Pro 64 English selected upgrade
Microsoft Productivity Software None
Memory 16 GB LPDDR5X-6400MHz (Soldered)
Solid State Drive 256 GB SSD M.2 2280 PCIe Gen4 TLC Opal
Display 14" WUXGA (1920 x 1200), IPS, Anti-Glare, Non-Touch, 100%sRGB, 400 nits, 60Hz, Low Power, Low Blue Light selected upgrade
Graphic Card Integrated Graphics
Camera 5MP RGB+IR with Microphone selected upgrade
Color Thunder Black Wireless Qualcomm Wi-Fi 6E NFA725A 2x2 AX & Bluetooth® 5.1 or above Integrated
Mobile Broadband No Wireless WAN
Ethernet Wired Ethernet
Fingerprint Reader No Fingerprint Reader
Keyboard Backlit, Black - English (US) selected upgrade System
Expansion Slots No Smart Card Reader
TPM Setting Enabled Discrete TPM2.0 Absolute BIOS Selection BIOS Absolute Enabled
Battery 4 Cell Li-Polymer 52.5Wh selected upgrade
Power Cord 65W USB-C Low Cost 90% PCC 2pin
AC Adapter - US
Electronic Privacy Filter No ePrivacy Filter
Language Pack Publication - Polish/Portuguese/English

I'll finalize by saying, while my system came with windows, I never booted it. When the computer arrived, I opened the chassis, removed the NVME SSD and placed it to the side for future use.

I installed a Samsung 970 EVO Plus NVME M.2 SSD

Test cases to follow.

Test case Number 1:

UEFI Bios: R2FET36W (1.16) Embedded Controller: R3FHT30W (1.14)

Begin by entering bios settings, and choosing Setup Defaults / Factory Defaults. exit bios with a save and reboot.

Boot Certified Ubuntu Image (Install Media from USB):
Ubuntu-T14G4-T16G2-P16sG2-P14sG4-P16v-AMD-20230905-529.iso
Sha1sum: d190346a53f44ab323c6a6eb00fbc412c67dbb07

Options chosen during install: Ubuntu Recovery: Restore entire Hard Drive.

Removed instillation media and reboot when prompted.

During the reboot, I observed the following error message:
"amd_gpio AMDI0030: Invalid config param 0014"

Do not configure network during instillation. Do not generate recovery media at this time.

The instillation performed a reboot.
During the reboot, I observed the following error message: "amd_gpio AMDI0030: Invalid config param 0014"

Upon bootup, I logged in to Gnome

uname -a results in:
Linux jrs-t14 6.1..0-1020-oem #20-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 16 13:40:16 UTC 2023 x86_64 x86_64 GNU/Linux

• I ran the command: sudo systemctl suspend,
• I waited 60 second with they system suspended.
• I pressed the Enter key to resume from suspend.

System soft rebooted with a bios error:
2204: System configuration data is invalid.
Press Esc to continue

Attaching Kernel Logs from Test 1

> journalctl -k -b -1

Unfortunately, welcome to the club; there are a few related threads:

https://forums.lenovo.com/t5/Debian/P14s-Gen-4-AMD-Reboots-While-Sleeping/m-p/5256532

https://forums.lenovo.com/t5/Other-Linux-Discussions/P14s-G4-AMD-failing-resume-from-suspend/m-p/5286501?page=1#6241697

https://forums.lenovo.com/t5/Other-Linux-Discussions/Arch-Linux-P14s-Gen3-suddenly-can-no-longer-hibernate-and-takes-forever-to-boot/m-p/5273899.

Hopefully we'll see this addressed one day soon.

Thanks for the clearly written and detailed analysis.

Notes have been added to the internal ticket (LO-2848). We've been trying to reproduce (with no joy so far) but will look to get some details from the FW team as to what might trigger this. A note that it's almost Chinese New Year so that will introduce some delays.

Mark

Test 2: Ubuntu 22.04.3 LTS w/ linux-oem-22.04d

To continue establishing a baseline this is my next test. 

• UEFI Bios: R2FET36W (1.16) Embedded Controller: R3FHT30W (1.14)
• Burn 22.04.3 LTS install media to USB.
• Install to system, with the following options:
  
  • Choose DO NOT connect network during install (so all package version info will remain known)
  • Choose "Normal Instillation"
  • Choose DO NOT "Install third party software for graphics and Wi-Fi hardware additional media formats
  • Choose "Erase disk and install Ubuntu" with no advanced features selected
  • Upon Instillation completion, the installer performs a scheduled reboot.
  • Enable networking
  • Upgrade Kernel to linux-oem-22.04d
    • sudo apt install linux-oem-22.04d
  • Reboot the system
  • Verify new kernel version
    • uname -a
    • Linux 6.5.0-1013-oem #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 08:57:02 UTC 2024 x86_64 x86_64 GNU/Linux
• Suspend test 2.A
  • timedatectl && sleep 3 && sudo systemctl suspend
  • using stopwatch, wait approximately 60 seconds
  • press Enter to Resume from Suspend
  • test results:
    • system performs soft reboot on resume, with error message:
    • 2204: System configuration data in invalid
    • Press Esc to continue
  • Note: suspend happened at approximately: 2024-02-02 21:52:09
  • I don't believe there is anything of interest in the kernel logs at or slightly after that time...
    • PM: suspend entry (s2idle)

Attaching Kernel Logs from Test 2A

• jouralctl -k -b -1 > kenel_logs_slowcamp_test_2A.txt

When/where exactly in the boot process do you see?

2204: System configuration data is invalid.

If I have that also I have always missed that...

@guest29835 While I can't comment for the OP, I see this when the system posts right after the soft reboot. After acknowledging this message, the system posts again and tends to boot normally, but it never resumes.