After updates last week I have a machine that now hangs when rebooting. The console reports: Reached target Shutdown reboot: Restarting system And thats it. It never (well, I only actually waited 60 hour) reboots. I'm guessing the console lines ... Failed unmounting /tmp and Failed unmounting /var ... have something to do with this, but I am at a loss as to how to proceed. These are local partitions, Linux 3.11.10-7-desktop x86_64 Thanks! -- Mike G. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-14 15:12 (GMT-0400) Mike Grau composed:
After updates last week I have a machine that now hangs when rebooting.
What hardware (esp. 'lspci | grep VGA'), and what video driver is X using?
The console reports:
Reached target Shutdown reboot: Restarting system
And thats it. It never (well, I only actually waited 60 hour) reboots.
I'm guessing the console lines ...
Failed unmounting /tmp
and
Failed unmounting /var
To see if mounts are or may be a red herring, try logging in on a tty as root and 'umount -a' to see what messages result before trying to reboot or shutdown. While there you could also try lsof to maybe see if something is running that might want to interfere with shutdown or reboot.
... have something to do with this, but I am at a loss as to how to proceed. These are local partitions, Linux 3.11.10-7-desktop x86_64
I wonder if this is related to https://bugzilla.novell.com/show_bug.cgi?id=850531 in some way? Try booting with noplymouth and/or plymouth.enable=0 and/or splash=0 on cmdline to see if the problem goes away. If the result pleases you, uninstall plymouth. See also: http://smithfarm-thebrain.blogspot.com/2012/11/opensuse-disable-graphical-sc... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/14/2014 02:49 PM the voices made Felix Miata write:
On 2014-04-14 15:12 (GMT-0400) Mike Grau composed:
After updates last week I have a machine that now hangs when rebooting.
What hardware (esp. 'lspci | grep VGA'), and what video driver is X using?
03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) Video driver appears to be mgag200
To see if mounts are or may be a red herring, try logging in on a tty as root and 'umount -a' to see what messages result before trying to reboot or shutdown. While there you could also try lsof to maybe see if something is running that might want to interfere with shutdown or reboot.
The umount does appear to be a read herring. With splash=0 I see they are ultimately unmounted.
https://bugzilla.novell.com/show_bug.cgi?id=850531 in some way? Try booting with noplymouth and/or plymouth.enable=0 and/or splash=0 on cmdline to see if the problem goes away. If the result pleases you, uninstall plymouth.
No good, I'm afraid. I tried all of the boot option above and the reboot process always hangs at reboot: Starting system That is also the last message when rebooting from "runlevel 3", failsafe, or single user mode. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-14 16:23 (GMT-0500) Mike Grau composed:
On 04/14/2014 02:49 PM the voices made Felix Miata write:
On 2014-04-14 14:12 (GMT-0500) Mike Grau composed:
After updates last week I have a machine that now hangs when rebooting.
What hardware (esp. 'lspci | grep VGA'), and what video driver is X using?
03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)
Video driver appears to be mgag200
If you look at https://bugzilla.novell.com/show_bug.cgi?id=823658 and the links therein you may get that same sense that I do that that particular chip is quirky, and could be the root of your problem.
To see if mounts are or may be a red herring, try logging in on a tty as root and 'umount -a' to see what messages result before trying to reboot or shutdown. While there you could also try lsof to maybe see if something is running that might want to interfere with shutdown or reboot.
The umount does appear to be a read herring. With splash=0 I see they are ultimately unmounted.
https://bugzilla.novell.com/show_bug.cgi?id=850531 in some way? Try booting with noplymouth and/or plymouth.enable=0 and/or splash=0 on cmdline to see if the problem goes away. If the result pleases you, uninstall plymouth.
No good, I'm afraid. I tried all of the boot option above and the reboot process always hangs at
reboot: Starting system
That is also the last message when rebooting from "runlevel 3", failsafe, or single user mode.
Did you try uninstalling plymouth? Maybe one of these describes your problem: https://bugzilla.novell.com/show_bug.cgi?id=864211 https://bugzilla.novell.com/show_bug.cgi?id=865433 https://bugzilla.novell.com/show_bug.cgi?id=862168 https://bugzilla.novell.com/show_bug.cgi?id=861489 https://bugzilla.novell.com/show_bug.cgi?id=860476 https://bugzilla.novell.com/show_bug.cgi?id=855115 https://bugzilla.novell.com/show_bug.cgi?id=867069 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 14/04/2014 16:12, Mike Grau ha scritto:
After updates last week I have a machine that now hangs when rebooting. The console reports:
Reached target Shutdown reboot: Restarting system
And thats it. It never (well, I only actually waited 60 hour) reboots.
I'm guessing the console lines ...
Failed unmounting /tmp
and
Failed unmounting /var
... have something to do with this, but I am at a loss as to how to proceed. These are local partitions, Linux 3.11.10-7-desktop x86_64
Thanks! -- Mike G.
Hi Mike, Just a guess! It could be /var or /tmp or both be full or even something weird happened there. Try to boot in rescue mode to give it a deeper look. Good luck! -- Marco Calistri (amdturion) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Marco Calistri <marco.calistri@yahoo.com.br> [04-14-14 17:58]:
Il 14/04/2014 16:12, Mike Grau ha scritto:
After updates last week I have a machine that now hangs when rebooting. The console reports:
Reached target Shutdown reboot: Restarting system
And thats it. It never (well, I only actually waited 60 hour) reboots.
I'm guessing the console lines ...
Failed unmounting /tmp
and
Failed unmounting /var
... have something to do with this, but I am at a loss as to how to proceed. These are local partitions, Linux 3.11.10-7-desktop x86_64
Hi Mike,
Just a guess!
It could be /var or /tmp or both be full or even something weird happened there.
Try to boot in rescue mode to give it a deeper look.
Or maybe the system is waiting for the journal to complete it's write ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 14/04/14 16:12, Mike Grau escribió:
After updates last week I have a machine that now hangs when rebooting. The console reports:
Reached target Shutdown reboot: Restarting system
And thats it. It never (well, I only actually waited 60 hour) reboots.
I'm guessing the console lines ...
Failed unmounting /tmp
and
Failed unmounting /var
... have something to do with this, but I am at a loss as to how to proceed. These are local partitions, Linux 3.11.10-7-desktop x86_64
Thanks! -- Mike G.
Follow the steps here --> http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 attach shutdown-log.txt to take a look. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Follow the steps here --> http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
attach shutdown-log.txt to take a look.
This appears to be a kernel issue as "sync && reboot -f" fails. -- Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 16/04/14 12:03, Mike Grau escribió:
Follow the steps here --> http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
attach shutdown-log.txt to take a look.
This appears to be a kernel issue as "sync && reboot -f" fails.
ah, ok. mention that in a bug report, otherwise whoever is going to review it is going to shoot the messenger or be derailed into debugging something that is not at fault. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
ah, ok. mention that in a bug report, otherwise whoever is going to review it is going to shoot the messenger or be derailed into debugging something that is not at fault.
Bug 874152 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-14 19:59 (GMT-0300) Cristian Rodríguez composed:
Follow the steps here --> http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
attach shutdown-log.txt to take a look.
My problem with 13.1 host big31 does not occur on every boot. It seems OK if I boot only multi-user and only ever login as root. Following booted to multi-user, but a non-root user logged in and ran startx for a few minutes, and thereafter shutdown suffered a considerable delay. http://fm.no-ip.com/Tmp/SUSE/shutdown-log-big31-131.txt If I understand what I see: 1-shutdown begins @either ~735 or ~866 2-@900 Timer elapsed on systemd-tmpfiles-clean.timer 3-58 second delay before next action @958: user@2000.service stopping timed out. Killing. 4-@959 debug log written and shutdown completes What kind of existing bug to search for and/or how what to write in a new one I could use guidance for. This is not my only 13.1 installation that has a long pause at shutdown time. I haven't inventoried which do and don't, or what processes may precipitate a hang. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Cristian Rodríguez -
Felix Miata -
Marco Calistri -
Mike Grau -
Patrick Shanahan