Laptop sometimes hangs on POST

schard · 2024-08-02 07:14:15

Since a couple of months I have the issue that my Lenovo Z16 sometimes hangs during POST.
This issue occurs only, but not always, if the laptop was suspended during its operation before the last poweroff (shutdown).

The symptoms then are, that when I press the power button, the laptop will power on an show the Lenovo EFI splash screen with the hint to press enter to interrupt normal startup.
However, waiting for up to 2h, the system does never advance past this point, nor does hitting enter result in any reaction from the EFI.
When in this state, even powering the system off via the power button (even if additionally unplugging and/or re-plugging it from the AC adapter) does not change this failure state.
This means, that even when I power off the system, wait (and maybe even disconnect it from the power outlet), the system, when powered on again, will return to this state, i.e. a hung EFI.
The only means that I know of at the moment to get the system running again, is to power off the system, disconnect the AC adapter *and* pressing the battery disconnect switch on its bottom before turning it on again.

I use fwupdmgr to regularly update any firmware, which is currently up-to-date.

What can I do to investigate and maybe even solve this issue?

Journal of last boot

Head_on_a_Stick · 2024-08-02 16:46:33

Have you tried removing the CMOS battery on the motherboard or triggering the reset mechanism (if it has one)?

My ASUS laptop will occasionally freeze before the boot logo shows but it does resolve after several minutes, a search says it's some sort of self-diagnostic "feature". Doesn't sound like this applies to you though if you waited 2 hours

EDIT: I suppose we could check the NVRAM, see if there are any redundant boot entries that might be clogging things up:

efibootmgr -u

Last edited by Head_on_a_Stick (2024-08-02 16:51:35)

schard · 2024-08-05 10:34:25

Regarding the CMOS battery: I did not check it yet, since I would need to screw open the laptop casing for that (every time).

The EFI boot entries do look normal to me:

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,001B,001C,001D,001E,001F,0020,0021,0022,0000
Boot0000* Linux-Firmware-Updater	HD(1,GPT,ce2a8954-b4ad-4578-92ce-961fdc51cc25,0x800,0x200000)/\EFI\arch\shimx64.efi\fwupdx64.efi
Boot0001* Arch Linux	HD(1,GPT,ce2a8954-b4ad-4578-92ce-961fdc51cc25,0x800,0x200000)/\vmlinuz-linuxroot=UUID=9c1ed4e7-ba4b-4359-8544-98d1e2c29174 rd.luks.uuid=22c73e20-a13b-48b2-8728-55e5be5a8131 rw initrd=\amd-ucode.img initrd=\initramfs-linux.img random.trust_cpu=on quiet splash initcall_blacklist=simpledrm_platform_driver_init
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics	FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  Asset Information	FvFile(da465b87-a26f-4c12-b78a-0361428fa026)
Boot0015  Regulatory Information	FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot0016  ThinkShield secure wipe	FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0017  ThinkShield Passwordless Power-On Device Manager	FvFile(08448b41-7f83-49be-82a7-0e84790ab133)
Boot0018  Wi-Fi Configuration	FvFile(d3aaff0f-cb22-4792-896c-802c2e9383ba)-App
Boot0019  Startup Interrupt Menu	FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot001A  Rescue and Recovery	FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot001B* USB CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot001C* USB FDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot001D* NVMe0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001E* ATA HDD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001F* USB HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0020* PXE BOOT	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0021* LENOVO CLOUD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
Boot0022* ON-PREMISE	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri()
Boot0023* Boot Next Boot Option	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)

kermit63 · 2024-08-05 12:13:33

This is a long shot, but do you have any USB devices connected to the laptop when powering up?

This happened to me a few years back, albeit on a desktop computer. A failing USB port prevented the UEFI firmware from sporadically accessing the device connected to the port, However, the UEFI firmware needed to check if that device is bootable before showing the boot screen, hence display is stuck waiting at the logo screen.

Simply detaching the device from the failing port allowed the boot process to continue in my case.

schard · 2024-08-05 13:39:58

Yes and no. Currently I'm in the office where I have my desktop screen connected to the laptop via USB-C which serves as
1) Power supply
2) External screen
3) USB hub

However, this also happens when I work from home, where I usually just have the original USB-C power supply connected.
Nonetheless, I'll try reproducing it without any external devices connected.

seth · 2024-08-05 14:57:30

This issue occurs only, but not always, if the laptop was suspended during its operation before the last poweroff (shutdown).

There several threads reg. Lenovo and STR, some relate to actions reg. the Lid and external power supply (basically you suspend and resume and everything is fine, but you suspend and close the lid or detach from/attach to a charger and all hell breaks loose)

Aug 01 13:10:51 archlinux kernel: ACPI: \_SB_.PCI0.GP11: Overriding _PRW sleep state (S4) by S0 from power resources
Aug 01 13:10:51 archlinux kernel: ACPI: \_SB_.PCI0.GP12: Overriding _PRW sleep state (S4) by S0 from power resources
Aug 01 13:10:51 archlinux kernel: ACPI: \_SB_.PCI0.GP19.NHI0: Overriding _PRW sleep state (S3) by S0 from power resources
Aug 01 13:10:51 archlinux kernel: ACPI: \_SB_.PCI0.GP19.NHI1: Overriding _PRW sleep state (S3) by S0 from power resources

cat /sys/power/mem_sleep

S3 (deep) or s2idle?

schard · 2024-08-06 08:05:50

I think you're on to something there:

~> cat /sys/power/mem_sleep                                                       2024-08-06T10:05:07
[s2idle]
~>

seth · 2024-08-06 08:56:05

s2idle is the only supported default for many modern systems, you'd typically have to engage in some firmware "hacks" (secret shortcuts etc) to get S3 enabled.
The problem with the latter is the "unsupported" part and the ability to throw off the ACPI, but not your case.

The problem with s2idle is that the system isn't actually sleeping and still handles events.
See whether you can reliably reproduce this through environmental changes (eg. lid or charger) or delay (sleep duration) and whether you can then combat this w/ a sleep cycle that does not include such events. If it's not related to the previously reported lid and charger events, radio would be a good contender and rfkill around the sleep might mitigate it.

schard · 2024-08-08 07:01:17

Alas, I couldn't find any S2/S3 settings in the EFI setup menu that I could tinker with.
However, the other day I was able to power on the laptop after it froze by soft-powering it off, then disconnecting the A/C adapter, letting the laptop sit for a couple of minutes and then powering it on again (without any external devices connected).
I would also consider moving from suspending the laptop in battery mode to hibernating it.
But...

[root@der-geraet neumann]# echo s2idle > /sys/power/mem_sleep
[root@der-geraet neumann]# echo shallow > /sys/power/mem_sleep
bash: echo: write error: Invalid argument
[root@der-geraet neumann]# echo deep > /sys/power/mem_sleep
bash: echo: write error: Invalid argument
[root@der-geraet neumann]# cat /sys/power/mem_sleep
[s2idle]
[root@der-geraet neumann]#

seth · 2024-08-08 09:36:33

As mentioned, the S3 option isn't regularly exposed in the firmware, you'll actually have to find and invoke some secret shortcuts/menu maneuvers to even get that option (if at all) - I'd not bother, recent threads suggest that while S3 has worked for a while on some lenovo systems, firmware updates rather broke it.

s2idle is the only option, but you still can https://wiki.archlinux.org/title/Power_ … ibernation the system, S3 isn't a prerequisite for S4 at all.

Arch Linux

#1 2024-08-02 07:14:15

Laptop sometimes hangs on POST

#2 2024-08-02 16:46:33

Re: Laptop sometimes hangs on POST

#3 2024-08-05 10:34:25

Re: Laptop sometimes hangs on POST

#4 2024-08-05 12:13:33

Re: Laptop sometimes hangs on POST

#5 2024-08-05 13:39:58

Re: Laptop sometimes hangs on POST

#6 2024-08-05 14:57:30

Re: Laptop sometimes hangs on POST

#7 2024-08-06 08:05:50

Re: Laptop sometimes hangs on POST

#8 2024-08-06 08:56:05

Re: Laptop sometimes hangs on POST

#9 2024-08-08 07:01:17

Re: Laptop sometimes hangs on POST

#10 2024-08-08 09:36:33

Re: Laptop sometimes hangs on POST

Board footer