Am 21.10.2016 um 08:42 schrieb Stephan Kulow:

Am 20.10.2016 um 23:38 schrieb Greg Freemyer:

...

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.

We see something very similiar in openqa:

https://openqa.opensuse.org/tests/287112#step/console_shutdown/1

So yes, I think there is a big problem still in.

I did some research today and from what it looks like, at least in the openqa case, the problem is KDE. During reboot, all possible KDE applications crash in QtSql and systemd writes out core dumps. While this is going on, the shutdown stalls. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Fri, Oct 21, 2016 at 9:28 AM, Cristian Rodríguez wrote:

On Thu, Oct 20, 2016 at 6:38 PM, Greg Freemyer 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

On Tue, Oct 25, 2016 at 4:05 PM, Oliver Kurz wrote:

On Friday 21 October 2016 12:04:14 Greg Freemyer wrote:

...

On Fri, Oct 21, 2016 at 9:28 AM, Cristian Rodríguez

wrote:

...

On Thu, Oct 20, 2016 at 6:38 PM, Greg Freemyer 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.

The corresponding test code used by openQA is https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests...

What you could do is * follow the installation guide to setup openQA locally on a machine of yours * reproduce a test locally * change the test code accordingly to what is mentioned for "debugging" * provide a pull request with the change to execute the debugging steps

If you need help regarding openQA the corresponding IRC channel is irc://chat.freenode.net/opensuse-factory

I may be able to try in a couple days. In the mean time I've tried numerous reboots of my test machine and I've had no luck reproducing. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org