[SOLVED] watchdog did not stop on reboot

MickeyKnox · 2013-12-09 11:21:36

Just recently after an upgrade (nothing special, i think), the following problem manifestet itself in my system:

When i reboot my computer, this message is presented to me:

watchdog watchdog0: watchdog did not stop!

It stays there for one or two minutes, until the computer finally reboots.

poweroff also takes forever now, however, the message is not presented then.

This has been reported before, about a year ago, unfortunately it seems not to have been solved:
https://bbs.archlinux.org/viewtopic.php?pid=1195597

How can i fix this?

Last edited by MickeyKnox (2013-12-10 14:46:12)

qinohe · 2013-12-09 11:51:31

We don't have a crystal ball, so you gonna have to provide much more info, if you would like us to help you.

As brain0 says in post #6, this a very normal behavior.

You need to figure out which process is taking so long.

Have a look at 'journalctl -b'.

karol · 2013-12-09 11:53:15

I get this message too, but my system shuts down / reboots immediately.

qinohe · 2013-12-09 11:57:18

karol wrote:

I get this message too, but my system shuts down / reboots immediately.

Yeah, I think anyone using watchdog will see this, but it's only a message, and watchdog will act if it goes beyond the 'time' specified in /etc/systemd/system.conf, if I understand correct.

MickeyKnox · 2013-12-09 22:07:38

qinohe wrote:

As brain0 says in post #6, this a very normal behavior.
You need to figure out which process is taking so long.

So you're saying the too are not relatet? The watchdog message and the reboot taking forever?

qinohe wrote:

Have a look at 'journalctl -b'.

I tried journalctl -b with several offsets, but the output was always the same:

-- Logs begin at Sun 2013-11-03 22:04:16 CET, end at Mon 2013-12-09 22:15:45 CET. --
Dec 09 22:15:44 skynet systemd[11699]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
Dec 09 22:15:44 skynet systemd[11699]: Mounted /sys/kernel/config.
Dec 09 22:15:44 skynet systemd[11699]: Stopped target Bluetooth.
Dec 09 22:15:44 skynet systemd[11699]: Stopped target Sound Card.
Dec 09 22:15:44 skynet systemd[11699]: Starting Default.
Dec 09 22:15:44 skynet systemd[11699]: Reached target Default.
Dec 09 22:15:44 skynet systemd[11699]: Startup finished in 149ms.

I coundn't make much sense of it...

qinohe · 2013-12-10 11:49:19

MickeyKnox wrote:

So you're saying the too are not relatet? The watchdog message and the reboot taking forever?

I didn't say that, well the watchdog is nothing more then, I quote the wiki

wiki wrote:

is an electronic timer that is used to detect and recover from computer malfunctions.

Thus by using watchdog you have the ability to recover from a say kernel crash.
So if the watchdog times out it should after a timed period restore the PC in a workable state.
This very practical for a server or machine you don't have access to.

So if you would not have the watchdog enabled, your system would probably still hang.

qinohe wrote:

Have a look at 'journalctl -b'.

I tried journalctl -b with several offsets, but the output was always the same:

-- Logs begin at Sun 2013-11-03 22:04:16 CET, end at Mon 2013-12-09 22:15:45 CET. --
Dec 09 22:15:44 skynet systemd[11699]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
Dec 09 22:15:44 skynet systemd[11699]: Mounted /sys/kernel/config.
Dec 09 22:15:44 skynet systemd[11699]: Stopped target Bluetooth.
Dec 09 22:15:44 skynet systemd[11699]: Stopped target Sound Card.
Dec 09 22:15:44 skynet systemd[11699]: Starting Default.
Dec 09 22:15:44 skynet systemd[11699]: Reached target Default.
Dec 09 22:15:44 skynet systemd[11699]: Startup finished in 149ms.

I coundn't make much sense of it...

Are you fully up to date?, cause I remember I had trouble restarting with the for last kernel (3.12.2-1 taht was I think), but since my laptop is on almost 24/7, it didn't bother me that much..

mojtabazn · 2013-12-10 12:35:38

as you say it happen from shutdown i think you should run command for pervious shutdown try this, that shows info about last boot and go to end an check what coused that time for shutdown

sudo journalctl -b -1

this shows pervious boot log
press end to go to end of log and then with up arrow go up until see this message it is bold

System is powering down

then chek where it takes much time than normal

for example this is mine for last shut down:

Dec 10 15:47:33 mojtaba systemd-logind[325]: System is powering down.

Deleted log for complete log see bottom link  

Dec 10 15:47:36 mojtaba systemd[1]: Shutting down.
Dec 10 15:47:36 mojtaba systemd-journal[173]: Journal stopped

complete log

http://privatepaste.com/d9a0846a12

MickeyKnox · 2013-12-10 14:45:32

Running journalctl with root privileges showed way more information. I didn't even consider that.

The problem seems to be some mounted cifs filesystems causing the system to be severely slowed on shut down.
The watchdog message seems not to be related, i just didn't noted it before.

I opened a new thread for the cifs problem and marked this one as solved:
https://bbs.archlinux.org/viewtopic.php … 6#p1358776

Thanks for your help~

Last edited by MickeyKnox (2013-12-10 14:46:50)

Arch Linux

#1 2013-12-09 11:21:36

[SOLVED] watchdog did not stop on reboot

#2 2013-12-09 11:51:31

Re: [SOLVED] watchdog did not stop on reboot

#3 2013-12-09 11:53:15

Re: [SOLVED] watchdog did not stop on reboot

#4 2013-12-09 11:57:18

Re: [SOLVED] watchdog did not stop on reboot

#5 2013-12-09 22:07:38

Re: [SOLVED] watchdog did not stop on reboot

#6 2013-12-10 11:49:19

Re: [SOLVED] watchdog did not stop on reboot

#7 2013-12-10 12:35:38

Re: [SOLVED] watchdog did not stop on reboot

#8 2013-12-10 14:45:32

Re: [SOLVED] watchdog did not stop on reboot

Board footer