Bug#952729: systemd: poweroff and reboot don't work
Control: reassign -1 src:linux Control: found -1 4.19.98-1 Hi Janusz On Tue, 17 Mar 2020 07:28:50 +0100 jsb...@mimuw.edu.pl (Janusz S. =?utf-8?Q?Bie=C5=84?=) wrote: > On Thu, Mar 12 2020 at 21:14 +01, Michael Biebl wrote: > > Hi > > > > Am 12.03.20 um 19:07 schrieb Janusz S. Bień: > >> On Wed, Mar 11 2020 at 15:23 +01, Michael Biebl wrote: > >>> Am 11.03.20 um 15:17 schrieb Janusz S. Bień: > >>> > Even if fwupdf is not the real culprit, it definitely slows down the > attempted shutdown. Shiuld I do something about? > >>> > >>> You can purge the fwupd package. This should be rather safe. > >> > >> It appeared there are more problems with fwupd: > >> > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953679 > >> > >> It actually doesn't start at boot: > >> > >> Mar 12 07:47:25 debian systemd[1]: fwupd.service: Start operation timed > >> > >> Can it be a systemd problem? Anyway, do you have any idea how to > >> diagnose it? > > Looks like I solved the problem with fwupd. Do you see any essential > change in the enclosed log? > At this point I don't see any systemd related errors anymore in the journal. I thus assume it's a kernel issue, which does not properly power off your system. So re-assigning accordingly. Regards, Michael signature.asc Description: OpenPGP digital signature
Bug#952729: systemd: poweroff and reboot don't work
Hi Am 12.03.20 um 19:07 schrieb Janusz S. Bień: > On Wed, Mar 11 2020 at 15:23 +01, Michael Biebl wrote: >> Am 11.03.20 um 15:17 schrieb Janusz S. Bień: >> >>> Even if fwupdf is not the real culprit, it definitely slows down the >>> attempted shutdown. Shiuld I do something about? >> >> You can purge the fwupd package. This should be rather safe. > > It appeared there are more problems with fwupd: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953679 > > It actually doesn't start at boot: > > Mar 12 07:47:25 debian systemd[1]: fwupd.service: Start operation timed > > Can it be a systemd problem? Anyway, do you have any idea how to > diagnose it? Not really. I'm not really familiar with fwupd. Its functionality is entirely optional though and if it causes problems on your system, my suggestion would be to uninstall the fwupd package. Michael signature.asc Description: OpenPGP digital signature
Bug#952729: systemd: poweroff and reboot don't work
On Wed, Mar 11 2020 at 15:23 +01, Michael Biebl wrote: > Am 11.03.20 um 15:17 schrieb Janusz S. Bień: > >> Even if fwupdf is not the real culprit, it definitely slows down the >> attempted shutdown. Shiuld I do something about? > > You can purge the fwupd package. This should be rather safe. It appeared there are more problems with fwupd: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953679 It actually doesn't start at boot: Mar 12 07:47:25 debian systemd[1]: fwupd.service: Start operation timed Can it be a systemd problem? Anyway, do you have any idea how to diagnose it? Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#952729: systemd: poweroff and reboot don't work
Am 11.03.20 um 15:17 schrieb Janusz S. Bień: > Even if fwupdf is not the real culprit, it definitely slows down the > attempted shutdown. Shiuld I do something about? You can purge the fwupd package. This should be rather safe. > BTW, any idea why I cannot open VT 9? It is worth to be investigated? That late during the shutdown process I assume the debug shell has already been killed by the final killing spree. signature.asc Description: OpenPGP digital signature
Bug#952729: systemd: poweroff and reboot don't work
On Wed, Mar 04 2020 at 17:47 +01, Janusz S. Bień wrote: > On Tue, Mar 03 2020 at 13:34 +01, Janusz S. Bień wrote: > > [...] > >> This happened yesterday after the poweroff from the Gnome shell >> menu. Unfortunately the photo I made is barery readable: >> >> https://photos.app.goo.gl/tXshKUsLXBHYYvQR6 >> >> Moreover I have a feeling that after pressing the power button there 1-2 >> lines of some output. > > A better photo: > > https://photos.app.goo.gl/zrKAE1dYLdxQ5Y6L9 > > There were several seconds between the last and the last-but-one message. Even if fwupdf is not the real culprit, it definitely slows down the attempted shutdown. Shiuld I do something about? BTW, any idea why I cannot open VT 9? It is worth to be investigated? Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#952729: systemd: poweroff and reboot don't work
On Fri, Feb 28 2020 at 13:47 +01, Janusz S. Bień wrote: > On Fri, Feb 28 2020 at 12:57 +01, Michael Biebl wrote: > > [...] > >> 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". > > Unfortunately after 'systemctl poweroff' the screen goes blank in a > fraction of second (on all consoles I tested)... > > It happened earlier that some text was displayed till I powered off > manually. This happened yesterday after the poweroff from the Gnome shell menu. Unfortunately the photo I made is barery readable: https://photos.app.goo.gl/tXshKUsLXBHYYvQR6 Moreover I have a feeling that after pressing the power button there 1-2 lines of some output. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#952729: systemd: poweroff and reboot don't work
On Fri, Feb 28 2020 at 12:57 +01, Michael Biebl wrote: [...] > 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". Unfortunately after 'systemctl poweroff' the screen goes blank in a fraction of second (on all consoles I tested)... It happened earlier that some text was displayed till I powered off manually. I have no idea how to reproduce it now - something changed in my system or am I doing something differently? I had a quick look at https://github.com/systemd/systemd/issues/5433 Should adding printk.devkmsg=on help somehow? Regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#952729: systemd: poweroff and reboot don't work
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
Bug#952729: systemd: poweroff and reboot don't work
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? Regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#952729: systemd: poweroff and reboot don't work
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. signature.asc Description: OpenPGP digital signature
