[Bug 1129476] New: Random 1m30s delay (timeout?) at shutdown
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 Bug ID: 1129476 Summary: Random 1m30s delay (timeout?) at shutdown Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: mail@studiobp.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 800285 --> http://bugzilla.opensuse.org/attachment.cgi?id=800285&action=edit Journal for a correct reboot Often, but not always, a delay is seen at shutdown, apparently limited to 1m30s by a timeout, on a pretty default Gnome install on an "Optimus" laptop. Seen on all tested builds of 15.1beta, currently at 429.2 Seems a regression, not seen in Leap 15.0 or previous openSUSE IIRC. Please find attached the journal for a correct reboot and for a delayed one, but I don't see any meaningful cue. Feel free to ask for additional logs or tests, usual suspects like USB, external filesystems, network, Plymouth not apparently involved. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c1 --- Comment #1 from Bruno Pesavento <mail@studiobp.org> --- Created attachment 800286 --> http://bugzilla.opensuse.org/attachment.cgi?id=800286&action=edit Journal for a reboot delayed 1m30s after "Reached target Shutdown" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c2 --- Comment #2 from Bruno Pesavento <mail@studiobp.org> --- I can reproduce the bug also with lightdm+lxqt desktop (3 out of 4 tries) so the problem is not limited to the Gnome desktop apparently. But I was unable to reproduce it booting to a console so far (multi user target), so it might be related to graphical targets. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c3 --- Comment #3 from Bruno Pesavento <mail@studiobp.org> --- Trying to debug this problem, I saw that the problem doesn't show up if booting with the following sequence.
boot to multi-user.target (just adding '3' to the boot command line) login as root and issue 'systemctl isolate graphical.target' on VT1 login as normal desktop user via GDM (desktop shows on VT2) logout as 'root' from VT1 work on the desktop (VT2) as usual, reboot or shutdown from desktop when finished. To me that looks like something goes wrong in the 'default' boot sequence, maybe the graphical target is started too soon on this HW (fast SSD and i7 4700HQ here) and starting it manually a few seconds later sorts things out? Tried that 5 times with no problem; tried again the 'default' boot directly to graphical desktop and the nasty 1m30s delay at shutdown was still there... Hope this helps somebody make sense of this annoying situation.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c4 Ed Vaessen <evaessen@ziggo.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |evaessen@ziggo.nl --- Comment #4 from Ed Vaessen <evaessen@ziggo.nl> --- I had the same problem. Among many lines, the shutdown log showed these: [ 77.019608] systemd-journald[473]: systemd-journald stopped as pid 473 [ 167.020886] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 167.027376] systemd-shutdown[1]: Sending SIGKILL to PID 484 (lvmetad). As I do not need the LVM, I deleted the following packages: liblvm2app2_2 liblvm2cmd2_02 lvm2 The service has vanished and shutdown is no longer delayed now. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c5 --- Comment #5 from Bruno Pesavento <mail@studiobp.org> --- Apparently setting the lvm2-monitor service to start "manually" and possibly stopping the lvm2-lvmtad and lvm2-lvmpolld services seems to be enough to solve the problem. Done 10 reboots without problems, I would have seen 6 or 7 delayed reboots with the default services config. BTW, updated to the current released version in the meantime. lvm as the culprit seems to be confirmed by at least one other user, see: https://forums.opensuse.org/showthread.php/536145-OpenSuSE-Leap-15-1-shutdow... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c6 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net --- Comment #6 from Felix Miata <mrmazda@earthlink.net> --- Created attachment 814397 --> http://bugzilla.opensuse.org/attachment.cgi?id=814397&action=edit # journalctl -b -1 | egrep -i 'ailed|atchd|boot|down' | egrep -vi 'sata|bootl' Not stopping watchdog I'm seeing painfully often. This last is from a 15.1 installation that had last been zypper up'd two months ago, running kernel 28.7, updated on the boot to 28.13. I removed the three lvm2 rpms, and shutdown became like Fedora's normal, virtually instant. The previous instance of watchdog not stopping and long shutdown delay was same PC booted to 15.0 only minutes before first boot of the day to 15.1. Neither of these produced a countdown timer reporting delay as often appears stopping a service that never started in the first place. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c8 Mischa Salle <mischa.salle@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mischa.salle@gmail.com --- Comment #8 from Mischa Salle <mischa.salle@gmail.com> --- the better solution is the one-line fix from https://github.com/lvmteam/lvm2/issues/17 since it works *with* LVM. I had the same issue (on a new 15.1 and actually using LVM so can't just remove the package) and this fixes it. Note that bugs https://bugzilla.opensuse.org/show_bug.cgi?id=1096241 and https://bugzilla.opensuse.org/show_bug.cgi?id=1142587 (both for Tumbleweed) are most probably the same. The required upstream patch can be found at https://sourceware.org/git/?p=lvm2.git;a=blobdiff;f=scripts/lvm2_lvmetad_sys... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mrmazda@earthlink.net | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c12 Axel Wein <axel.wein@online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |axel.wein@online.de --- Comment #12 from Axel Wein <axel.wein@online.de> --- I think I have the same issue with Leap 15.2 (German). But it is more extreme. The shutdown often has a delay of 1:30 m, yes. Starting up uses 2:40 m (openSUSE 13.2 it was 1:25 m on the same machine). I can't delete LVM! systemd-analyze plot shows about 1:31 m for initrd. But the terrible thing is, that booting up (not only rebooting) very often ends with "Administratorpasswort für Wartungszwecke eingeben (oder drücken Sie Strg + D, um fortzufahren)" - so I can't use the OS really. I'm not so firm with Linux yet, that I could change the initrd like it is described above. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129476 http://bugzilla.opensuse.org/show_bug.cgi?id=1129476#c13 --- Comment #13 from heming zhao <heming.zhao@suse.com> --- (In reply to Axel Wein from comment #12)
I think I have the same issue with Leap 15.2 (German). But it is more extreme. The shutdown often has a delay of 1:30 m, yes. Starting up uses 2:40 m (openSUSE 13.2 it was 1:25 m on the same machine).
I can't delete LVM!
systemd-analyze plot shows about 1:31 m for initrd. But the terrible thing is, that booting up (not only rebooting) very often ends with "Administratorpasswort für Wartungszwecke eingeben (oder drücken Sie Strg + D, um fortzufahren)" - so I can't use the OS really.
I'm not so firm with Linux yet, that I could change the initrd like it is described above.
this bug title related with lvmetad. in leap 15.2, lvm2 doesn't have lvmetad code. you boot/shutdown issue is another issue. if you very concern this issue, please file a new bug. when you file a bug, please upload below info. - supportconfig - systemd-analyze plot - system booting/rebooting or shutting down log. ``` add kernel cmdline: splash=verbose systemd.show_status=0 rd.break=pre-shutdown rd.break=shutdown delete "spash=silent quiet" using ctrl-d to break hung when booting/rebooting/shutingdown. ``` -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com