Mailinglist Archive: opensuse-bugs (6470 mails)

< Previous Next >
[Bug 1138984] Fresh system installation does not shutdown
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 16 Jul 2019 08:46:03 +0000
  • Message-id: <bug-1138984-21960-87DF4nicdS@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1138984
http://bugzilla.suse.com/show_bug.cgi?id=1138984#c3

Franck Bui <fbui@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID

--- Comment #3 from Franck Bui <fbui@xxxxxxxx> ---
(In reply to Alynx Zhou from comment #1)
Maybe you'd better use `poweroff` instead `halt`, because it seems that
`halt` may not send ACPI instruction but poweroff do send, which leads
hangs, because halt terminates system but does not tell computer to
shutdown, so your screen is still on and it looks like hangs.

Indeed so the fact that the shutdown process hangs forever with halt is
expected. If you don't want this behavior, uses something like "reboot",
"poweroff"...

Regarding the umount failures, the one regarding /var is a known issue as
journald is still writing logs in the journal until very lately.

For the other ones... I don't know, but it's a different issue which should be
reported in a new bug. So please open a new bug if you want us to look at them
but make sure to provide the debug logs.

For providing the debug logs:

- make sure to use persistent journals:
# mkdir /var/log/journal
# reboot

- before rebooting turn the debug logs on:
# systemd-analyze log-level debug

- reboot

- provide the debug logs from the previous boot:
# journalctl -b -1 -o short-monotonic

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >