Am 28.02.20 um 10:00 schrieb Janusz S. Bień: > On Fri, Feb 28 2020 at 9:25 +01, Michael Biebl wrote: >> Am 28.02.20 um 08:17 schrieb Janusz S. Bień: >>> Package: systemd >>> Version: 241-7~deb10u3 >>> Severity: normal >>> >>> Dear Maintainer, >>> >>> This is a fresh install of buster on a just bought HP 15-rb063nw >>> (7SG28EA) laptop. Following the suggestions found in the Internet I >>> tried adding to GRUB_CMDLINE_LINUX_DEFAULT options acpi=force, >>> acpi=noirq, modeset but to no avail (some options made additional >>> problems). So I started to follow the instructions in >>> /usr/share/doc/systemd/README.Debian.gz. Unfortunately for an unknown >>> reason I was unable to swiych to VT9, so switched on logging to >>> shutdown-log.tx. I enclose the file. >> >> Thanks for the shutdown log. >> I shows, that systemd did properly shutdown the system right to the >> point where it issues the reboot() syscall. >> >> https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/src/shutdown/shutdown.c#L576 >> >> At this point, the kernel is responsible for finally powering >> off/rebooting your system. >> So your problem appears to be kernel related. > > Many thanks for your quick answer. > > So what I should do? Reassign the bug to the kernel? Can you do it for me?
Could you snap a picture when your kernel hangs on shutdown? Use the same kernel command line options as you did for creating the shutdown log and also drop "quiet".
signature.asc
Description: OpenPGP digital signature
