[SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

Moises · 2021-11-13 17:18:21

I have version 5.15.2-arch1-1 and I'm dual booting with Windows.

It never finishes shutting down, and I don't know what causes it. I removed quiet splash from the grub configuration, so I see

[OK] Reached target System Shutdown.
[OK] Reached target Late Shutdown Services.
[OK] Finished System Reboot
[OK] Reached target System Reboot
kauditd_printk_skb: 16 callbacks suppressed
watchdog: watchdog0: watchdog did not stop!

The the screen goes black, but it never actually powers off.

Output of journalctl -b -1

Output of journalctl -k -b -1

I apologize in advance if I'm missing important information.

Last edited by Moises (2021-11-14 16:19:09)

seth · 2021-11-13 20:41:19

I'm dual booting with Windows

3rd link below, rule that out.

Moises · 2021-11-14 07:01:12

3rd link below, rule that out.

Thank you! It's disabled and it hasn't fixed the problem. I can mount the windows partition without getting a message that I have to mount it in write only mode.

However, rereading that link I've realized that I'm not supposed to have two EFI system partitions, so I messed up the installation. Maybe this is an extremely dumb question, but can I get away with not formatting and reinstalling? I'm really hoping that eventually (soon) I'll convince myself that I don't need windows and that I'm capable of using Linux without breaking everything, and then I won't have dual booting problems.

V1del · 2021-11-14 10:48:24

If you can boot the system then having two ESPs shouldn't be a problem and it's almost certainly not the reason for the issue you're experiencing.

seth · 2021-11-14 13:49:05

Can you suspend to RAM?

Moises · 2021-11-14 15:11:36

seth wrote:

Can you suspend to RAM?

I don't think so. I ran

 sudo rtcwake --mode mem --seconds 10 --verbose

and then screen went black and didn't come back.

journalctl after trying to suspend

seth · 2021-11-14 15:16:58

ACPI issue, did you check whether there're comments for your notebook model, https://wiki.archlinux.org/title/Laptop/Lenovo ?

Moises · 2021-11-14 15:36:32

There's a comment about "Annoying messages about AMD-Vi", but that's it. Power management is "not tested".

I'm confused about well, what acpi is, but also what brought this problem. I think the first time it happened was after upgrading from version 5.14.16-arch1-1 to 5.15.2, but I've already tried undoing that upgrade and it didn't fix the issue.

seth · 2021-11-14 15:40:27

https://en.wikipedia.org/wiki/Advanced_ … _Interface - the way the OS tells the BIOS to power off etc.

What's the exact notebook model? (The wiki has the brand labels and I'm in no mood to research the BIOS version string ;-)

Moises · 2021-11-14 15:50:06

It's Ideapad 320-15ABR, and inside /sys/class/dmi/id/bios_version is 5QCN21WW.

Moises · 2021-11-14 16:01:30

Progress/I did something stupid: It shuts down correctly with 5.14.16. The last time I tried it I rebooted only once, and then thought that it hadn't worked, but now I've realized I'm probably supposed to reboot twice to check, and indeed it works.

I apologize, I didn't mean to ask for a lesson about hardware, I was just trying to set the expectations about my (lack of) understanding of things.

seth · 2021-11-14 16:12:05

The last time I tried it I rebooted only once

You mean after disabling windows fast-start?
Yeah, rebooting both OS a couple of times (well, twice) can be required to straighten the ACPI table.

If the problem doesn't re-emerge, please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

FRT: The specific model has btw. complaints on similar power state control issues all across the interwebz - including this forum … https://bbs.archlinux.org/viewtopic.php?id=233856
So it *might* have worked by fluke…

Moises · 2021-11-14 16:18:09

You mean after disabling windows fast-start?

I'll explain myself better: windows fast-start was disabled all along. The problem is still there if I upgrade to Linux 5.15, but it is gone if I go back to Linux 5.14.

One last question: where do I go from here? Should I keep my package database frozen in time, while periodically checking if a new update fixes the problem? Should I report a bug?

seth · 2021-11-14 20:53:05

You could try the LTS kernel, use that, keep the linux kernel updating and if the problem doesn't go away, you should file an upstream bug.
You may also want to bisect the issue, https://wiki.archlinux.org/title/Kernel … egressions & https://wiki.archlinux.org/title/Bisect

Moises · 2021-11-14 21:31:04

Thank you so much for the help!!!

Arch Linux

#1 2021-11-13 17:18:21

[SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#2 2021-11-13 20:41:19

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#3 2021-11-14 07:01:12

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#4 2021-11-14 10:48:24

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#5 2021-11-14 13:49:05

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#6 2021-11-14 15:11:36

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#7 2021-11-14 15:16:58

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#8 2021-11-14 15:36:32

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#9 2021-11-14 15:40:27

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#10 2021-11-14 15:50:06

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#11 2021-11-14 16:01:30

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#12 2021-11-14 16:12:05

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#13 2021-11-14 16:18:09

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#14 2021-11-14 20:53:05

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

#15 2021-11-14 21:31:04

Re: [SOLVED] Shutdown never finishes: "Sending SIGTERM to remaining pr..."

Board footer