[SOLVED] After recent update the reboot doesn't work

webcapcha · 2024-04-25 19:34:13

The reboot was working like a charm but since few days ago if I reboot it doesn't work.
The actual result is it's going to reboot shut down services according to logs it even turn off the screen but the power led indicator remains active and nothing happened. I mean, it doesn't turn on the laptop even after 90 seconds. I have to hold power button to turn it off and then power on the laptop. I did not do any configs I assume it's some package was updated and issued a bug.

Here is a pacman logs
https://0x0.st/XHMT.txt

Here is a reboot logs
https://0x0.st/XHMB.txt

Last edited by webcapcha (2024-04-29 08:46:43)

Nikolai5 · 2024-04-26 07:01:10

Many users running AMD 7 series GPUs reported this issue, but that's been resolved for a while now with kernel updates I believe.

Can you tell us what hardware you're running? Dual GPU? Nvidia or AMD and what model? Are you dual booting with Windows and have you disabled Windows fast boot?

seth · 2024-04-26 08:06:06

https://bbs.archlinux.org/viewtopic.php?id=294821 - but tthe provided journal tail doesn't allow to gage whether the HW and kernel versions match that.

webcapcha · 2024-04-27 04:30:59

Can you tell us what hardware you're running? Dual GPU? Nvidia or AMD and what model? Are you dual booting with Windows and have you disabled Windows fast boot?

only Arch with ext4 + lvm

but tthe provided journal tail doesn't allow to gage whether the HW and kernel versions match that

I beleive it's also kernel related. I was tried with LTS kernel and looks like reboot works with it.
here is devise specs
https://0x0.st/XHMo.txt

seth · 2024-04-27 07:18:25

You're running the hardened kernel, though - also a problem w/ the non-hardenend one?
Commonalities are ryzen, plasma, sddm
No nvidia, though. And different board/vendor.

Do you see sth. like https://i.ibb.co/yk4dvvC/archlinux-reboot-fails.jpg

webcapcha · 2024-04-27 10:27:06

Do you see sth. like https://i.ibb.co/yk4dvvC/archlinux-reboot-fails.jpg

I don't think so.

I've filmed all reboot process.
https://photos.app.goo.gl/proyCmhYJYbZZwpU8 (just for the video purpose I didn't wait long before press the power button, but few times I was waiting a long period. Around three minutes I guess, nothing happened)

With LTS kernel it looks like it works. But during day I've noticed fun fact. If I tried to reboot just after the Laptop is booted it works well. For example boot the Laptop, open a browser and reboot in a few minutes. In this scenario it works well.
But if the laptop has been working for a few hours then video above will show how it's proceed with reboot

Do you suggest to test it with regular kernel? That nuance with "few hours to catch the bag" is making harder to say clearly is it work or not

I'm little bit scary is it possible that laptop trying to "do something with uefi" when it's in that stage?

seth · 2024-04-27 16:13:17

The video results in 500 (server error) when trying to play or download it.

cat video.mp4 | curl -F 'file=@-' 0x0.st

webcapcha · 2024-04-27 16:24:23

Interesting why google photos gives 500 error for you.

https://0x0.st/XHym.mp4

loqs · 2024-04-27 17:32:20

webcapcha wrote:

Do you suggest to test it with regular kernel?

Do you have a different way to test if the issue can be triggered without the hardened patch set / config changes?

Last edited by loqs (2024-04-27 17:32:33)

seth · 2024-04-27 21:17:17

So basically it just doesn't repower.
You could try whether any of the

        reboot=                [KNL]
                        Format (x86 or x86_64):
                                [w[arm] | c[old] | h[ard] | s[oft] | g[pio]] | d[efault] \
                                [[,]s[mp]#### \
                                [[,]b[ios] | a[cpi] | k[bd] | t[riple] | e[fi] | p[ci]] \
                                [[,]f[orce]
                        Where reboot_mode is one of warm (soft) or cold (hard) or gpio
                                        (prefix with 'panic_' to set mode for panic
                                        reboot only),
                              reboot_type is one of bios, acpi, kbd, triple, efi, or pci,
                              reboot_force is either force or not specified,
                              reboot_cpu is s[mp]#### with #### being the processor
                                        to be used for rebooting.

parameters has sanitizing impact here, but first try the non-hardened kernel.

webcapcha · 2024-04-28 12:03:40

I did some testing. The same behavior with regular kernel and even with lts kernel. Maybe its somehow related with sleep. If the laptop did sleep, after wake up the reboot doesn't work.

But it's definitely related to some of the recent update (since 20 of April) because on this laptop I didn't do any configs since that and before the reboot was working ideally in any case. Maybe it's amd ucode package? Could it be hardware issue, something broke?

webcapcha · 2024-04-28 12:12:21

added
I did test with Fedora 39 live cd, reboot and power off work great. Even after sleep (suspend)

seth · 2024-04-28 13:59:11

What if you log out of KDE, isolate the multi-user.target (2nd link below) and shutdown/reboot from there?

webcapcha · 2024-04-28 14:05:52

Didn't help.

sudo systemctl isolate multi-user.target

did actually work because when I log out of Plasma and run that command I see on ctrl+alt+f1/f2 regular tty login prompt instead of sddm.

But reboot still has issue

loqs · 2024-04-28 14:32:55

Did it start with 6.8.7? https://gitlab.archlinux.org/archlinux/ … /issues/45

webcapcha · 2024-04-28 14:42:20

With regular kernel I have the same issue.
Name : linux
Version : 6.8.7.arch1-2

Did test today's morning. But I have an idea that the bug is reproducible after the laptop did at least 1 sleep. Is it a simple way to go back for the latest 6.7 kernel branch.

The bugreport above is kinda similar.

Last edited by webcapcha (2024-04-28 14:43:33)

loqs · 2024-04-28 14:46:14

I would first try downgrading the kernel to 6.8.6.

webcapcha · 2024-04-28 14:50:13

What if I don't have 6.8.6 in my pacman cache, because I was using hardened kernel and did install regular kernel only today for testing purpose.

seth · 2024-04-28 14:52:35

https://wiki.archlinux.org/title/Ala

webcapcha · 2024-04-28 15:04:57

I can't tell for 100% because as I mentioned above sometimes it takes some time the bug to be reproducible, but

OMG looks like 6.8.6 kernel is really solve the issue. At least quick test with 1. boot 2. sleep 3 wake up 4 reboot is working good.

Oh, I even had bad thoughts that something related to hardware issue.

This topic helps me to study how to downgrade kernel, how to switch between kernels and how to add the entries to the systemd-boot. Now I can do this with closed eyes. Yeah

By the way why linux-lts is affected?

webcapcha · 2024-04-28 15:06:31

Should I report that my laptop also affected on the link above? Can we also get a fix for hardened kernel?

Added

looks like 6.8.6 kernel is about 13 April. My assumption that issue is after 20 Apr was correct. Happy

Last edited by webcapcha (2024-04-28 15:11:31)

seth · 2024-04-28 15:18:20

If the LTS kernel is affected as well but 6.8.6 isn't then the bogus commit has been backported or it's the kernel config.
@loqs, has anyone tried the 6.8.6 kernel w/ the 6.8.7 config or vv?

webcapcha · 2024-04-28 15:25:07

General thoughts. I am looking at the logs from the first message here and last records there is systemd PID 1. I thought systemd is the last worker who is responsible to shutdown a machine similar as systemd is the first one who is doing the job when power on the machine.

But looks like kernel is in action too

loqs · 2024-04-28 15:29:48

seth wrote:

@loqs, has anyone tried the 6.8.6 kernel w/ the 6.8.7 config or vv?

Not that I know of. The three config changes I can see are two from upstream related to BHI mitigation:
https://git.kernel.org/pub/scm/linux/ke … 7a9f983509
https://git.kernel.org/pub/scm/linux/ke … a8f43b0bcd
Locally Arch disabling the N_GSM module:
https://gitlab.archlinux.org/archlinux/ … 1cc66e0f24
Edit:
Building 6.8.6 with the config from 6.8.7.

Last edited by loqs (2024-04-28 15:38:34)

seth · 2024-04-28 15:49:37

Locally Arch disabling the N_GSM module

That would be funny. And absurd

6.6.27-1 and 6.6.28-1 have the BHI changes
@webcapcha, you probably tried the 6.6.28-1 LTS kernel, can you reproduce this w/ the 6.6.27-1 or 6.6.26-1 ones?

Arch Linux

#1 2024-04-25 19:34:13

[SOLVED] After recent update the reboot doesn't work

#2 2024-04-26 07:01:10

Re: [SOLVED] After recent update the reboot doesn't work

#3 2024-04-26 08:06:06

Re: [SOLVED] After recent update the reboot doesn't work

#4 2024-04-27 04:30:59

Re: [SOLVED] After recent update the reboot doesn't work

#5 2024-04-27 07:18:25

Re: [SOLVED] After recent update the reboot doesn't work

#6 2024-04-27 10:27:06

Re: [SOLVED] After recent update the reboot doesn't work

#7 2024-04-27 16:13:17

Re: [SOLVED] After recent update the reboot doesn't work

#8 2024-04-27 16:24:23

Re: [SOLVED] After recent update the reboot doesn't work

#9 2024-04-27 17:32:20

Re: [SOLVED] After recent update the reboot doesn't work

#10 2024-04-27 21:17:17

Re: [SOLVED] After recent update the reboot doesn't work

#11 2024-04-28 12:03:40

Re: [SOLVED] After recent update the reboot doesn't work

#12 2024-04-28 12:12:21

Re: [SOLVED] After recent update the reboot doesn't work

#13 2024-04-28 13:59:11

Re: [SOLVED] After recent update the reboot doesn't work

#14 2024-04-28 14:05:52

Re: [SOLVED] After recent update the reboot doesn't work

#15 2024-04-28 14:32:55

Re: [SOLVED] After recent update the reboot doesn't work

#16 2024-04-28 14:42:20

Re: [SOLVED] After recent update the reboot doesn't work

#17 2024-04-28 14:46:14

Re: [SOLVED] After recent update the reboot doesn't work

#18 2024-04-28 14:50:13

Re: [SOLVED] After recent update the reboot doesn't work

#19 2024-04-28 14:52:35

Re: [SOLVED] After recent update the reboot doesn't work

#20 2024-04-28 15:04:57

Re: [SOLVED] After recent update the reboot doesn't work

#21 2024-04-28 15:06:31

Re: [SOLVED] After recent update the reboot doesn't work

#22 2024-04-28 15:18:20

Re: [SOLVED] After recent update the reboot doesn't work

#23 2024-04-28 15:25:07

Re: [SOLVED] After recent update the reboot doesn't work

#24 2024-04-28 15:29:48

Re: [SOLVED] After recent update the reboot doesn't work

#25 2024-04-28 15:49:37

Re: [SOLVED] After recent update the reboot doesn't work

Board footer