Mailinglist Archive: opensuse (924 mails)

< Previous Next >
[opensuse] Shutdown sometimes hangs
  • From: Andrea Turrini <andrea.turrini@xxxxxxxxx>
  • Date: Mon, 8 Oct 2012 14:11:06 +0200
  • Message-id: <CAFaemE-WmxW4UC7hKE0jFLr615=Y3nBGMm66R8R_G7mFS_aDOA@mail.gmail.com>
Hi all,

sometimes I face a strange problem on shutdown: it simply hangs until
I press Ctrl-Alt-Del several times (the required number of times is
random).
At screen I see that plymouth fails and log contains:

Oct 07 22:41:57 orodruin.lotr xdm[28730]: Shutting down service lightdm..done
Oct 07 22:41:57 orodruin.lotr vboxdrv[28808]: Stopping VirtualBox
kernel modules..done
Oct 07 22:41:58 orodruin.lotr network-remotefs[28789]: Shutting down
(remotefs) network interfaces:
Oct 07 22:41:58 orodruin.lotr network-remotefs[28789]: Shutting down
service (remotefs) network . . . . . . . . ...done
Oct 07 22:41:59 orodruin.lotr network[29301]: Shutting down (localfs)
network interfaces:
Oct 07 22:41:59 orodruin.lotr network[29301]: eth0 device:
Atheros Communications Inc. AR8131 Gigabit Et
Oct 07 22:41:59 orodruin.lotr ifdown[29631]: eth0 device: Atheros
Communications Inc. AR8131 Gigabit Et
Oct 07 22:41:59 orodruin.lotr dhcpcd[29675]: eth0: dhcpcd not running
Oct 07 22:41:59 orodruin.lotr dhcpcd[29675]: eth0: exiting
Oct 07 22:42:00 orodruin.lotr network[29301]: ..done wlan0
device: Intel Corporation Centrino Wireless-N 1000
Oct 07 22:42:00 orodruin.lotr ifdown[29775]: wlan0 device: Intel
Corporation Centrino Wireless-N 1000
Oct 07 22:42:01 orodruin.lotr dhcpcd[29819]: wlan0: dhcpcd not running
Oct 07 22:42:01 orodruin.lotr dhcpcd[29819]: wlan0: exiting
Oct 07 22:42:03 orodruin.lotr network[29301]: ..doneShutting down
service (localfs) network . . . . . . . . ...done
Oct 07 22:42:41 orodruin.lotr systemd[1]: plymouth-reboot.service:
control process exited, code=exited status=69
Oct 07 22:42:41 orodruin.lotr systemd[1]: Unit plymouth-reboot.service
entered failed state.
Oct 07 22:42:51 orodruin.lotr systemd[1]: plymouth-reboot.service:
control process exited, code=exited status=69
Oct 07 22:42:51 orodruin.lotr systemd[1]: Unit plymouth-reboot.service
entered failed state.
Oct 07 22:43:09 orodruin.lotr systemd[1]: plymouth-reboot.service:
control process exited, code=exited status=69
Oct 07 22:43:09 orodruin.lotr systemd[1]: Unit plymouth-reboot.service
entered failed state.
Oct 07 22:43:13 orodruin.lotr systemd[1]: plymouth-reboot.service:
control process exited, code=exited status=69
Oct 07 22:43:13 orodruin.lotr systemd[1]: Unit plymouth-reboot.service
entered failed state.
[the same messages repeated several times]
Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service:
control process exited, code=exited status=69
Oct 07 22:43:21 orodruin.lotr systemd[1]: Unit plymouth-reboot.service
entered failed state.
Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service
start request repeated too quickly, refusing to start.
Oct 07 22:43:21 orodruin.lotr systemd[1]:
systemd-random-seed-save.service start request repeated too quickly,
refusing to start.
Oct 07 22:43:21 orodruin.lotr systemd[1]: alsa-store.service start
request repeated too quickly, refusing to start.
Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service
start request repeated too quickly, refusing to start.
Oct 07 22:43:21 orodruin.lotr systemd[1]:
systemd-random-seed-save.service start request repeated too quickly,
refusing to start.
Oct 07 22:43:21 orodruin.lotr systemd[1]: alsa-store.service start
request repeated too quickly, refusing to start.
Oct 07 22:43:22 orodruin.lotr systemd[1]: plymouth-reboot.service
start request repeated too quickly, refusing to start.
[the same messages repeated several times]
Oct 07 22:43:24 orodruin.lotr systemd[1]: plymouth-reboot.service
start request repeated too quickly, refusing to start.
Oct 07 22:43:24 orodruin.lotr systemd[1]:
systemd-random-seed-save.service start request repeated too quickly,
refusing to start.
Oct 07 22:43:24 orodruin.lotr systemd[1]: alsa-store.service start
request repeated too quickly, refusing to start.
Oct 07 22:43:27 orodruin.lotr systemd[1]: dbus.service stopping timed
out (2). Killing.
Oct 07 22:43:27 orodruin.lotr systemd[1]: Unit dbus.service entered
failed state.
Oct 07 22:43:27 orodruin.lotr systemd[1]: Shutting down.
Oct 07 22:43:27 orodruin.lotr systemctl[30129]: Failed to get D-Bus
connection: Connection terminated during authentication.
Oct 07 22:43:27 orodruin.lotr systemd-journal[282]: Journal stopped

(the line at 22:42:03 is as reported by systemd-journal, it is not a
copy&paste problem)
The first message at 22:42:41 should correspond to my first
Ctrl-Alt-Del as the splash was not animated, so I pressed Esc to see
the messages, the shutdown sequence was hanged and then I started to
press Ctrl-Alt-Del repeatedly (with shorter and shorter interval) to
force the shutdown.

On a regular shutdown, I obtain:

Oct 06 23:24:46 orodruin.lotr network[31080]: ..done wlan0
device: Intel Corporation Centrino Wireless-N 1000
Oct 06 23:24:46 orodruin.lotr ifdown[31558]: wlan0 device: Intel
Corporation Centrino Wireless-N 1000
Oct 06 23:24:46 orodruin.lotr dhcpcd[31602]: wlan0: dhcpcd not running
Oct 06 23:24:46 orodruin.lotr dhcpcd[31602]: wlan0: exiting
Oct 06 23:24:48 orodruin.lotr network[31080]: ..doneShutting down
service (localfs) network . . . . . . . . ...done
Oct 06 23:24:49 orodruin.lotr systemd[1]: Shutting down.
Oct 06 23:24:49 orodruin.lotr systemd-journal[276]: Journal stopped

So, since this is clearly a subject for a bug report, the question is:
against which component?

Best,
Andrea

PS: nothing has changed at system level between the two shutdowns
since no package has been installed/removed/updated.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >