T14s Gen 3 AMD won't come back after suspend

Hellmann · 2024-01-28 21:16:45

Hi,

I have a ThinkPad T14s Gen 3 AMD which runs mostly very good (everything is on the newest version). But for I guess one month (sadly I do not know when it started) now, I face a frustrating issue: sometimes (and i really mean sometimes) the laptop won't come back after it was suspended (either actively by me or passively by time). The display stays black, pressing power-button or trying to switch the tty does not do anything. I think it rather happens if it is plugged in, but thats just a feeling. I looked in journalctl with "journalctl -xb -b -1 | grep -iA 30 suspend", "journalctl -n 10000 -e" and dmesg but I didn't found anything. How can I further debug it?

From the arch-wiki (https://wiki.archlinux.org/title/Lenovo … AMD)_Gen_3) I have the /etc/udev/rules.d/99-battery.rules running, could that cause a issue? It seems that it is very similar to this: https://bbs.archlinux.org/viewtopic.php?id=285784

I'm thankfull for any help

Last edited by Hellmann (2024-01-28 21:18:56)

archuser8762 · 2024-01-30 11:26:41

I have the same problem (T14s G3 amd) which appeared first, like you said one month ago (never had this problem before). So far I wasn't able to debug this. Problem happens with plugged and unplugged power. Very annoying. -.- Iam not running the battery rules you mentioned. Reason for black screen seems to be somewhere else.

Last edited by archuser8762 (2024-01-30 11:28:58)

Hellmann · 2024-01-30 11:32:33

For me with the procedure you mentioned "Problem happens with plugged and unplugged power" it is kind of reproducible. But sometimes it happens even when it was unplugged the whole time. All logs are empty... very annoying.

Edit:

Maybe I found something:

Jan 30 13:05:01 mymachine fwupd[2860]: 12:05:01.100 FuPluginUpower failed to query lid state
Jan 30 13:05:01 mymachine fwupd[2860]: 12:05:01.100 FuPluginUpower failed to query lid state

Last edited by Hellmann (2024-01-30 12:10:33)

archuser8762 · 2024-01-30 13:44:38

Jan 25 22:48:45 host fwupd[25334]: 21:48:45.025 FuPluginUpower failed to query lid state
Jan 25 22:48:45 host fwupd[25334]: 21:48:45.025 FuPluginUpower failed to query lid state

But i didn't had a black screen at that time. Today I had a blackscreen after suspend at ~ 10.30am. But my log doesn't show anything suspicious?!

Jan 30 08:25:39 host wireplumber[1665]: [0:00:29.828140054] [1665] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Jan 30 10:46:41 host kernel: iommu: DMA domain TLB invalidation policy: lazy mode
Jan 30 10:46:45 host nm-dispatcher[1517]: Invalid MIT-MAGIC-COOKIE-1 key
Jan 30 10:46:45 host nm-dispatcher[1855]: Invalid MIT-MAGIC-COOKIE-1 key
Jan 30 10:46:45 host nm-dispatcher[1865]: Invalid MIT-MAGIC-COOKIE-1 key
Jan 30 10:46:45 host nm-dispatcher[1870]: Invalid MIT-MAGIC-COOKIE-1 key
Jan 30 10:46:49 host wireplumber[1970]: [0:00:45.598636277] [1970] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Jan 30 10:53:36 host NetworkManager[1462]: <warn> [1706608416.9606] dispatcher: (12) failed (after 0.004 sec): Could not activate remote peer: activation request failed: unit is invalid.
Jan 30 10:54:10 host kernel: iommu: DMA domain TLB invalidation policy: lazy mode
Jan 30 10:54:19 host wireplumber[1670]: [0:00:26.096442172] [1670] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Jan 30 11:52:07 host kernel: ACPI: button: The lid device is not compliant to SW_LID.

Hellmann · 2024-01-30 14:44:15

I opened a thread in the Lenovo forums: https://forums.lenovo.com/t5/Other-Linu … -p/5287076

gaelic · 2024-01-31 07:17:13

Hey, I have a z13 and experiencing the same problem (or very similar) since some time. I was not able to really pinpoint yet ... but it may be related to a combination of broken firmware and kernel driver of the ath11k, see https://bugzilla.kernel.org/show_bug.cgi?id=217239
What helped for me at the moment: I downgraded to kernel 6.6.7 for the moment and have no suspend issues.

PS: why I'm struggling to pinpoint is about the same experience as yours, sometimes it works, but sometimes the Laptop freezes.

Last edited by gaelic (2024-01-31 07:18:45)

Hellmann · 2024-01-31 09:02:01

Hi,

thank you for that information! I will edit my post in the Lenovo Forum with your hint.

gaelic · 2024-02-01 09:22:21

As I am not able to really pinpoint the issue to ath11k, it might also be related to bluetooth:

https://bugzilla.kernel.org/show_bug.cgi?id=218364

Multiple regressions at the same time ...

Hellmann · 2024-02-03 13:14:55

Hmm okay! Yes, it seems difficult to pinpoint the issue to something specific. In the Lenovo forums I had no answer so far...

gaelic · 2024-02-03 15:06:14

Yes, some had sucess with either new firmware versions or kernel updates. Some not.
Did you try kernel 6.6.7 by any chance?

Hellmann · 2024-02-04 15:21:04

No, I don't. I have become a father 4 weeks ago, so I don't have enough time to in depth testing. But as for that reason it is twice as annoying, because you often have to leave your laptop for some time. And then when you come back...

tubize · 2024-02-07 10:14:56

I'm also facing this problem on a T495s AMD laptop. Happens randomly and laptop freezes completely. SysRq REISUB does nothing. Started about a month ago I think.
Latest Bios, latest fwupd, and kernel 6.7.3. Updating to 6.7.4 right now but holding out little hope that it'll fix it.
I do get one error with journalctl -b -1 that might be of some use:

Feb 06 22:46:13 T49 systemd-sleep[374664]: Performing sleep operation 'suspend'...
Feb 06 22:46:13 T49 kernel: PM: suspend entry (deep)
Feb 06 22:46:13 T49 kernel: Filesystems sync: 0.005 seconds
Feb 06 22:46:14 T49 kernel: Freezing user space processes
Feb 06 22:46:14 T49 kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Feb 06 22:46:14 T49 kernel: OOM killer disabled.
Feb 06 22:46:14 T49 kernel: Freezing remaining freezable tasks
Feb 06 22:46:14 T49 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Feb 06 22:46:14 T49 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Feb 06 22:46:14 T49 kernel: systemd-sleep: page allocation failure: order:0, mode:0x100c02(GFP_NOIO|__GFP_HIGHMEM|__GFP_HARDWALL), nodemask=(null),cpuset=/,mems_allowed=0
Feb 06 22:46:14 T49 kernel: CPU: 1 PID: 374664 Comm: systemd-sleep Tainted: G           OE      6.7.3-arch1-1 #1 b8291227ebee24f0bec9b3471a94151938512264
Feb 06 22:46:14 T49 kernel: Hardware name: LENOVO 20NKS03P00/20NKS03P00, BIOS R12ET63W(1.33 ) 12/06/2023
Feb 06 22:46:14 T49 kernel: Call Trace:
Feb 06 22:46:14 T49 kernel:  <TASK>
Feb 06 22:46:14 T49 kernel:  dump_stack_lvl+0x47/0x60
Feb 06 22:46:14 T49 kernel:  warn_alloc+0x165/0x1e0
Feb 06 22:46:14 T49 kernel:  __alloc_pages_slowpath.constprop.0+0xd4f/0xdb0
Feb 06 22:46:14 T49 kernel:  __alloc_pages+0x32d/0x350
Feb 06 22:46:14 T49 kernel:  ttm_pool_alloc+0x19f/0x600 [ttm 5f4307115931a5f6e0dc38bb0184291ac9207725]
Feb 06 22:46:14 T49 kernel:  amdgpu_ttm_tt_populate+0x7c/0xb0 [amdgpu 3f66c94e9c076d4a73edf261cf98db7721227fae]
Feb 06 22:46:14 T49 kernel:  ttm_tt_populate+0xa1/0x130 [ttm 5f4307115931a5f6e0dc38bb0184291ac9207725]
Feb 06 22:46:14 T49 kernel:  ttm_bo_handle_move_mem+0x162/0x170 [ttm 5f4307115931a5f6e0dc38bb0184291ac9207725]
Feb 06 22:46:14 T49 kernel:  ttm_mem_evict_first+0x201/0x530 [ttm 5f4307115931a5f6e0dc38bb0184291ac9207725]
Feb 06 22:46:14 T49 kernel:  ttm_resource_manager_evict_all+0xa7/0x1d0 [ttm 5f4307115931a5f6e0dc38bb0184291ac9207725]
Feb 06 22:46:14 T49 kernel:  ? __pfx_pci_pm_prepare+0x10/0x10
Feb 06 22:46:14 T49 kernel:  amdgpu_device_prepare+0x4e/0xd0 [amdgpu 3f66c94e9c076d4a73edf261cf98db7721227fae]
Feb 06 22:46:14 T49 kernel:  pci_pm_prepare+0x34/0x70
Feb 06 22:46:14 T49 kernel:  dpm_prepare+0x269/0x440
Feb 06 22:46:14 T49 kernel:  dpm_suspend_start+0x1e/0x90
Feb 06 22:46:14 T49 kernel:  suspend_devices_and_enter+0x165/0x960
Feb 06 22:46:14 T49 kernel:  pm_suspend+0x25e/0x590
Feb 06 22:46:14 T49 kernel:  state_store+0x6c/0xd0
Feb 06 22:46:14 T49 kernel:  kernfs_fop_write_iter+0x136/0x1d0
Feb 06 22:46:14 T49 kernel:  vfs_write+0x23d/0x400
Feb 06 22:46:14 T49 kernel:  ksys_write+0x6f/0xf0
Feb 06 22:46:14 T49 kernel:  do_syscall_64+0x64/0xe0
Feb 06 22:46:14 T49 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 06 22:46:14 T49 kernel:  ? handle_mm_fault+0xa2/0x360
Feb 06 22:46:14 T49 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 06 22:46:14 T49 kernel:  ? do_user_addr_fault+0x304/0x670
Feb 06 22:46:14 T49 kernel:  ? srso_return_thunk+0x5/0x5f
Feb 06 22:46:14 T49 kernel:  ? exc_page_fault+0x7f/0x180
Feb 06 22:46:14 T49 kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0x76
Feb 06 22:46:14 T49 kernel: RIP: 0033:0x739433522044
Feb 06 22:46:14 T49 kernel: Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d 25 c3 0d 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 48 89 54 24 18 48
Feb 06 22:46:14 T49 kernel: RSP: 002b:00007ffee9008678 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Feb 06 22:46:14 T49 kernel: RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 0000739433522044
Feb 06 22:46:14 T49 kernel: RDX: 0000000000000004 RSI: 00005702c8ea00f0 RDI: 0000000000000005
Feb 06 22:46:14 T49 kernel: RBP: 00005702c8ea00f0 R08: 0000000000000000 R09: 0000000000000001
Feb 06 22:46:14 T49 kernel: R10: 0000000000000003 R11: 0000000000000202 R12: 0000000000000004
Feb 06 22:46:14 T49 kernel: R13: 00005702c8e9c2d0 R14: 00007394335f4f40 R15: 00000000fffffff7
Feb 06 22:46:14 T49 kernel:  </TASK>
Feb 06 22:46:14 T49 kernel: Mem-Info:
Feb 06 22:46:14 T49 kernel: active_anon:1235561 inactive_anon:142423 isolated_anon:0
                             active_file:286346 inactive_file:591412 isolated_file:0
                             unevictable:136 dirty:45 writeback:0
                             slab_reclaimable:40917 slab_unreclaimable:43603
                             mapped:160311 shmem:20083 pagetables:15903
                             sec_pagetables:0 bounce:0
                             kernel_misc_reclaimable:0
                             free:68666 free_pcp:2077 free_cma:0
Feb 06 22:46:14 T49 kernel: Node 0 active_anon:4942244kB inactive_anon:569692kB active_file:1145384kB inactive_file:2365648kB unevictable:544kB isolated(anon):0kB isolated(file):0kB mapped:641244kB dirty:180kB writeback:0kB shmem:80332kB shmem_thp:0kB shmem_pmdmapped:0kB anon_thp:991232kB writeback_tmp:0kB kernel_stack:28640kB pagetables:63612kB sec_pagetables:0kB all_unreclaimable? no
Feb 06 22:46:14 T49 kernel: Node 0 DMA free:13312kB boost:0kB min:72kB low:88kB high:104kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Feb 06 22:46:14 T49 kernel: lowmem_reserve[]: 0 2862 13810 13810 13810
Feb 06 22:46:14 T49 kernel: Node 0 DMA32 free:88924kB boost:31468kB min:45456kB low:48952kB high:52448kB reserved_highatomic:0KB active_anon:387444kB inactive_anon:82744kB active_file:122020kB inactive_file:786680kB unevictable:512kB writepending:0kB present:3029704kB managed:2963408kB mlocked:512kB bounce:0kB free_pcp:6296kB local_pcp:6296kB free_cma:0kB
Feb 06 22:46:14 T49 kernel: lowmem_reserve[]: 0 0 10948 10948 10948
Feb 06 22:46:14 T49 kernel: Node 0 Normal free:172428kB boost:120400kB min:173916kB low:187292kB high:200668kB reserved_highatomic:0KB active_anon:4555076kB inactive_anon:487224kB active_file:1023364kB inactive_file:1578968kB unevictable:32kB writepending:152kB present:11517952kB managed:11218084kB mlocked:32kB bounce:0kB free_pcp:2012kB local_pcp:2012kB free_cma:0kB
Feb 06 22:46:14 T49 kernel: lowmem_reserve[]: 0 0 0 0 0
Feb 06 22:46:14 T49 kernel: Node 0 DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB (U) 2*2048kB (UM) 2*4096kB (M) = 13312kB
Feb 06 22:46:14 T49 kernel: Node 0 DMA32: 21921*4kB (UM) 3*8kB (U) 6*16kB (U) 13*32kB (U) 3*64kB (U) 2*128kB (U) 1*256kB (U) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 88924kB
Feb 06 22:46:14 T49 kernel: Node 0 Normal: 12199*4kB (UME) 6686*8kB (UME) 3486*16kB (UME) 197*32kB (UME) 18*64kB (UM) 6*128kB (M) 4*256kB (M) 4*512kB (M) 3*1024kB (M) 0*2048kB 0*4096kB = 172428kB
Feb 06 22:46:14 T49 kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Feb 06 22:46:14 T49 kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Feb 06 22:46:14 T49 kernel: 903607 total pagecache pages
Feb 06 22:46:14 T49 kernel: 5776 pages in swap cache
Feb 06 22:46:14 T49 kernel: Free swap  = 180020kB
Feb 06 22:46:14 T49 kernel: Total swap = 1048572kB
Feb 06 22:46:14 T49 kernel: 3640912 pages RAM
Feb 06 22:46:14 T49 kernel: 0 pages HighMem/MovableOnly
Feb 06 22:46:14 T49 kernel: 91699 pages reserved
Feb 06 22:46:14 T49 kernel: 0 pages cma reserved
Feb 06 22:46:14 T49 kernel: 0 pages hwpoisoned
Feb 06 22:46:14 T49 kernel: [TTM] Buffer eviction failed
Feb 06 22:46:14 T49 kernel: [drm] evicting device resources failed
Feb 06 22:46:14 T49 kernel: amdgpu 0000:06:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x70 returns -12
Feb 06 22:46:14 T49 kernel: amdgpu 0000:06:00.0: PM: not prepared for power transition: code -12
Feb 06 22:46:14 T49 kernel: PM: Some devices failed to suspend, or early wake event detected
Feb 06 22:46:14 T49 kernel: OOM killer enabled.
Feb 06 22:46:14 T49 kernel: Restarting tasks ... done.
Feb 06 22:46:14 T49 kernel: random: crng reseeded on system resumption
Feb 06 22:46:14 T49 kernel: PM: suspend exit
Feb 06 22:46:14 T49 kernel: PM: suspend entry (s2idle)

ewaller · 2024-02-07 18:03:48

Hellmann wrote:

I have become a father 4 weeks ago, so I don't have enough time to in depth testing.

Congratulations. Remember, sleep is way overrated.

tubize · 2024-02-10 09:23:52

ewaller wrote:

Hellmann wrote:
I have become a father 4 weeks ago, so I don't have enough time to in depth testing.
Congratulations. Remember, sleep is way overrated.

Haha, yea no more S2idle for you Hellmann
With a bit of luck you'll reach S1; "a low wake latency sleeping state"

Arch Linux

#1 2024-01-28 21:16:45

T14s Gen 3 AMD won't come back after suspend

#2 2024-01-30 11:26:41

Re: T14s Gen 3 AMD won't come back after suspend

#3 2024-01-30 11:32:33

Re: T14s Gen 3 AMD won't come back after suspend

#4 2024-01-30 13:44:38

Re: T14s Gen 3 AMD won't come back after suspend

#5 2024-01-30 14:44:15

Re: T14s Gen 3 AMD won't come back after suspend

#6 2024-01-31 07:17:13

Re: T14s Gen 3 AMD won't come back after suspend

#7 2024-01-31 09:02:01

Re: T14s Gen 3 AMD won't come back after suspend

#8 2024-02-01 09:22:21

Re: T14s Gen 3 AMD won't come back after suspend

#9 2024-02-03 13:14:55

Re: T14s Gen 3 AMD won't come back after suspend

#10 2024-02-03 15:06:14

Re: T14s Gen 3 AMD won't come back after suspend

#11 2024-02-04 15:21:04

Re: T14s Gen 3 AMD won't come back after suspend

#12 2024-02-07 10:14:56

Re: T14s Gen 3 AMD won't come back after suspend

#13 2024-02-07 18:03:48

Re: T14s Gen 3 AMD won't come back after suspend

#14 2024-02-10 09:23:52

Re: T14s Gen 3 AMD won't come back after suspend

Board footer