On Fri, Oct 21, 2016 at 9:28 AM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
On Thu, Oct 20, 2016 at 6:38 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
I upgraded my 42.2 PC with each alpha/beta release.
Yesterday I updated to RC1 and then rebooted.
I just now rebooted via a SSH login. I was also sitting in front of the machine so I could watch it.
The console popped up the Leap Icon/Logo with the 3 big dots below it. The dots showed the machine was alive.
After 10 minutes I thought it was locked up and was trying alt-F2, etc. I may have hit cntrl-alt-delete. Then all of a sudden, the reboot proceeded.
..from PID 23432 (
So.. what hangs the shutdown ? follow the instructions here https://freedesktop.org/wiki/Software/systemd/Debugging/
Cheers.
(Adding Ludwig in CC.) I will attempt to, but I don't know how to reproduce it. It failed at least once in openQA. It is reproducible in openQA? https://openqa.opensuse.org/tests/287112#step/console_shutdown/1 If so, it may be that trying to debug it there is an option? The requested debug options don't seem to hard to implement in the openQA test, but I know little about openQA. From: https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 ================ If normal reboot or poweroff work, but take a suspiciously long time, then boot with the debug options: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 save the following script as /usr/lib/systemd/system-shutdown/debug.sh and make it executable: #!/bin/sh mount -o remount,rw / dmesg > /shutdown-log.txt mount -o remount,ro / reboot Look for timeouts logged in the resulting file shutdown-log.txt and/or attach it to a bugreport. ================ Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org