[opensuse-factory] Umm... 42.2 RC1 froze on shutdown for 12 minutes, then continued the reboot?
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. The machine was idle all day today. This is all the log entries from today from journalctl. Oct 20 17:14:16 Thermaltake systemd[3173]: Stopped target Default. Oct 20 17:14:16 Thermaltake systemd[3173]: Reached target Shutdown. Oct 20 17:14:16 Thermaltake systemd[3173]: Starting Exit the Session... Oct 20 17:14:16 Thermaltake systemd[3173]: Stopped target Basic System. Oct 20 17:14:16 Thermaltake systemd[3173]: Stopped target Timers. Oct 20 17:14:16 Thermaltake systemd[3173]: Stopped target Paths. Oct 20 17:14:16 Thermaltake systemd[3176]: pam_unix(systemd-user:session): sessi Oct 20 17:14:16 Thermaltake systemd[3173]: Stopped target Sockets. Oct 20 17:14:16 Thermaltake systemd[3173]: Received SIGRTMIN+24 from PID 23432 ( -- Reboot -- Oct 20 17:26:29 Thermaltake systemd[2119]: Reached target Timers. Oct 20 17:26:29 Thermaltake systemd[2119]: Reached target Paths. Oct 20 17:26:29 Thermaltake systemd[2119]: Reached target Sockets. Oct 20 17:26:29 Thermaltake systemd[2119]: Reached target Basic System. Oct 20 17:26:29 Thermaltake systemd[2119]: Reached target Default. Oct 20 17:26:29 Thermaltake systemd[2119]: Startup finished in 27ms. lines 11962-12010/12010 (END) So, it claims it did the startup in 27 msecs, but ignores that it took over 10 minutes to shutdown. This a desktop PC with 64GB of RAM and NVME SSD. I also had a 3TB USB drive connected to it and mounted. I'd done very little I/O to the USB drive between mounting it and rebooting. Today, -- Greg Freemyer Hillary says Trump is the only Republican she can beat, why should we vote for him? Evan McMullin is surging in the west of the Rockies Deny Hillary, vote Evan McMullin for President -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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. 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 2016-10-21 08:42, Stephan Kulow wrote:
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.
Try remove plymouth, remove "quiet", add "verbose", to get all boot/halt messages on the screen, thus try to find where it waits. On my test machine (vmplayer) console "poweroff" is very fast. No messages. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
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 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. -- 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 <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
On Friday 21 October 2016 12:04:14 Greg Freemyer wrote:
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.
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 Regards, Oliver -- 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 <okurz@suse.de> wrote:
On Friday 21 October 2016 12:04:14 Greg Freemyer wrote:
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.
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
participants (5)
-
Carlos E. R. -
Cristian Rodríguez -
Greg Freemyer -
Oliver Kurz -
Stephan Kulow