You are not logged in.

#1 2016-12-29 03:17:08

Thorned_Rose
Member
From: Auckland, New Zealand
Registered: 2015-12-30
Posts: 34

Silent shutdown. watchdog: watchdog0: watchdog did not stop!

I've got silent boot all good. But I cannot get silent shutdown. Restart/shutdown does not hang - it reboots or shuts down fine within seconds.

If I restart I get:

[    54.796241] watchdog: watchdog0: watchdog did not stop!
[    54.918590] watchdog: watchdog0: watchdog did not stop!
[    55.597358] reboot: Restarting system

If I shutdown I get:

[    222.679589] reboot: Power down

I know why the watchdog text appears (I've read about as much as I can find that's relevant on the Wiki, net and these forums) but I am yet to find how I can suppress the output of that text. I'm on a home desktop PC so it's not necessary for my computer to automagically reboot after 10 minutes if shutdown/reboot hangs.... can I remove/disable this watchdog timer from my system?
How I can suppress the reboot: lines of text?

System:
rose@visas-marr
OS: Arch Linux
Kernel: x86_64 Linux 4.8.13-1-ARCH
Uptime: 18m
Packages: 1249
Shell: bash 4.4.5
Resolution: 1920x1200
WM: Mutter(DeepinGala)
WM Theme: Arc-Darker deepin [GTK2], deepin [GTK3]
Icon Theme: deepin
Font: Noto Sans 11
CPU: Intel Core i5-6500 CPU @ 3.6GHz
GPU: GeForce GTX 950
RAM: 1858MiB / 15991MiB

System is completely up to date as of writing this.

Restart log (last 30 lines):

Dec 29 14:04:53 visas-marr systemd[1]: Deactivating swap /dev/disk/by-partuuid/061384d3-07b9-4540-b61f-6242ebfdb480...
Dec 29 14:04:53 visas-marr systemd[1]: Deactivating swap Swap Partition...
Dec 29 14:04:53 visas-marr systemd[1]: Unmounting /mnt/Farsight...
Dec 29 14:04:53 visas-marr systemd[1]: Unmounted /boot.
Dec 29 14:04:53 visas-marr systemd[1]: Stopped File System Check on /dev/disk/by-uuid/B1D5-6223.
Dec 29 14:04:53 visas-marr swapoff[5305]: swapoff: /dev/disk/by-uuid/ebed628d-7c27-42e1-b5f2-56f8ab459c3e: swapoff failed: Invalid argument
Dec 29 14:04:53 visas-marr systemd[1]: dev-disk-by\x2duuid-ebed628d\x2d7c27\x2d42e1\x2db5f2\x2d56f8ab459c3e.swap: Swap process exited, code=exited status=255
Dec 29 14:04:53 visas-marr systemd[1]: Deactivated swap /dev/disk/by-uuid/ebed628d-7c27-42e1-b5f2-56f8ab459c3e.
Dec 29 14:04:53 visas-marr systemd[1]: dev-disk-by\x2duuid-ebed628d\x2d7c27\x2d42e1\x2db5f2\x2d56f8ab459c3e.swap: Unit entered failed state.
Dec 29 14:04:53 visas-marr systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:17.0-ata-1-part2.
Dec 29 14:04:53 visas-marr systemd[1]: Deactivated swap /dev/disk/by-partuuid/061384d3-07b9-4540-b61f-6242ebfdb480.
Dec 29 14:04:53 visas-marr systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x50026b775c056f07-part2.
Dec 29 14:04:53 visas-marr systemd[1]: Deactivated swap /dev/disk/by-id/ata-KINGSTON_SV300S37A120G_50026B775C056F07-part2.
Dec 29 14:04:53 visas-marr systemd[1]: Deactivated swap Swap Partition.
Dec 29 14:04:54 visas-marr systemd[1]: Unmounted /mnt/Farsight.
Dec 29 14:04:54 visas-marr systemd[1]: Reached target Unmount All Filesystems.
Dec 29 14:04:54 visas-marr systemd[1]: Stopped File System Check on /dev/disk/by-uuid/1e3dcee6-a93f-430b-9209-92443cbfacd4.
Dec 29 14:04:54 visas-marr systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Dec 29 14:04:54 visas-marr systemd[1]: Stopped target Local File Systems (Pre).
Dec 29 14:04:54 visas-marr systemd[1]: Stopped Create Static Device Nodes in /dev.
Dec 29 14:04:54 visas-marr systemd[1]: Stopped Remount Root and Kernel File Systems.
Dec 29 14:04:54 visas-marr systemd[1]: Reached target Shutdown.
Dec 29 14:04:54 visas-marr systemd[1]: Reached target Final Step.
Dec 29 14:04:54 visas-marr systemd[1]: Starting Reboot...
Dec 29 14:04:54 visas-marr systemd[1]: Shutting down.
Dec 29 14:04:54 visas-marr systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Dec 29 14:04:54 visas-marr systemd[1]: Set hardware watchdog to 10min.
Dec 29 14:04:54 visas-marr kernel: watchdog: watchdog0: watchdog did not stop!
Dec 29 14:04:54 visas-marr kernel: systemd-shutdow: 40 output lines suppressed due to ratelimiting
Dec 29 14:04:54 visas-marr systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Dec 29 14:04:54 visas-marr systemd-journald[153]: Journal stopped

Restart log full: http://pastebin.com/dcz3zErq

Shutdown log (last 30 lines):

Dec 29 15:24:48 visas-marr systemd[1]: Unmounted /home/rose/Downloads.
Dec 29 15:24:48 visas-marr systemd[1]: Unmounted /run/user/1000.
Dec 29 15:24:48 visas-marr systemd[1]: Unmounted /home/rose/Pictures.
Dec 29 15:24:48 visas-marr systemd[1]: Unmounted Temporary Directory.
Dec 29 15:24:48 visas-marr systemd[1]: Stopped target Swap.
Dec 29 15:24:48 visas-marr systemd[1]: Deactivating swap /dev/disk/by-path/pci-0000:00:17.0-ata-1-part2...
Dec 29 15:24:48 visas-marr systemd[1]: Deactivating swap Swap Partition...
Dec 29 15:24:48 visas-marr systemd[1]: Unmounting /mnt/Farsight...
Dec 29 15:24:48 visas-marr swapoff[3659]: swapoff: /dev/sda2: swapoff failed: Invalid argument
Dec 29 15:24:48 visas-marr systemd[1]: dev-sda2.swap: Swap process exited, code=exited status=255
Dec 29 15:24:48 visas-marr systemd[1]: Deactivated swap Swap Partition.
Dec 29 15:24:48 visas-marr systemd[1]: dev-sda2.swap: Unit entered failed state.
Dec 29 15:24:48 visas-marr systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:17.0-ata-1-part2.
Dec 29 15:24:48 visas-marr systemd[1]: Deactivated swap /dev/disk/by-partuuid/061384d3-07b9-4540-b61f-6242ebfdb480.
Dec 29 15:24:48 visas-marr systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x50026b775c056f07-part2.
Dec 29 15:24:48 visas-marr systemd[1]: Deactivated swap /dev/disk/by-id/ata-KINGSTON_SV300S37A120G_50026B775C056F07-part2.
Dec 29 15:24:48 visas-marr systemd[1]: Deactivated swap /dev/disk/by-uuid/ebed628d-7c27-42e1-b5f2-56f8ab459c3e.
Dec 29 15:24:48 visas-marr systemd[1]: Unmounted /mnt/Farsight.
Dec 29 15:24:48 visas-marr systemd[1]: Reached target Unmount All Filesystems.
Dec 29 15:24:48 visas-marr systemd[1]: Stopped File System Check on /dev/disk/by-uuid/1e3dcee6-a93f-430b-9209-92443cbfacd4.
Dec 29 15:24:48 visas-marr systemd[1]: Stopped target Local File Systems (Pre).
Dec 29 15:24:48 visas-marr systemd[1]: Stopped Create Static Device Nodes in /dev.
Dec 29 15:24:48 visas-marr systemd[1]: Stopped Remount Root and Kernel File Systems.
Dec 29 15:24:48 visas-marr systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Dec 29 15:24:48 visas-marr systemd[1]: Reached target Shutdown.
Dec 29 15:24:48 visas-marr systemd[1]: Reached target Final Step.
Dec 29 15:24:48 visas-marr systemd[1]: Starting Power-Off...
Dec 29 15:24:48 visas-marr systemd[1]: Shutting down.
Dec 29 15:24:48 visas-marr kernel: systemd-shutdow: 40 output lines suppressed due to ratelimiting
Dec 29 15:24:48 visas-marr systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Dec 29 15:24:48 visas-marr systemd-journald[151]: Journal stopped

Shutdown log (full): http://pastebin.com/F0We8ymN

I followed the instructions at https://wiki.archlinux.org/index.php/Silent_boot (Kernal parameters and fsck) to get silent boot. I did not do anything under 'sysctl' because /etc/sysctl.d/20-quiet-printk.conf does not exist on my system (only a 99-sysctl.conf file exists in the sysctl.d directory).

Bootloader (systemd-boot) arch.conf:

## Arch Linux Boot entry

title   Arch Linux
linux   /vmlinuz-linux
initrd	/intel-ucode.img
initrd  /initramfs-linux.img
options root=PARTUUID=54faad9e-edd4-4d98-88cc-26af325d65a0 rw quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log-priority=3

Any help much appreciated, thank you smile

Offline

#2 2016-12-29 08:30:43

JohnBobSmith
Member
From: Canada
Registered: 2014-11-29
Posts: 742

Re: Silent shutdown. watchdog: watchdog0: watchdog did not stop!

If I am not mistaken as the the purpose and function of watchdog, you should be able to simply remove it with pacman. Then, double check the service files were purged or disabled and reboot to test.


I have been diagnosed with Bipolar Disorder. Therefore, I apologize in advance if the quality/content of my posts decline sharply, at any point.

Offline

#3 2016-12-29 15:40:56

rdeckard
Member
Registered: 2015-01-28
Posts: 125

Re: Silent shutdown. watchdog: watchdog0: watchdog did not stop!

Add "nowatchdog" to your kernel parameters. See the new wiki section on watchdogs: https://wiki.archlinux.org/index.php/Im … #Watchdogs

Offline

#4 2016-12-29 22:53:47

rdeckard
Member
Registered: 2015-01-28
Posts: 125

Re: Silent shutdown. watchdog: watchdog0: watchdog did not stop!

Additionally, if you are wanting to just suppress the messages you need to lower the loglevel to 1 in your boot parameters. The Wiki gives loglevel=3 as an example in the SIlent Boot article. However, if you lower the loglevel to 1 you are suppressing other possible important messages.

Offline

#5 2016-12-30 04:13:30

Thorned_Rose
Member
From: Auckland, New Zealand
Registered: 2015-12-30
Posts: 34

Re: Silent shutdown. watchdog: watchdog0: watchdog did not stop!

JohnBobSmith wrote:

If I am not mistaken as the the purpose and function of watchdog, you should be able to simply remove it with pacman. Then, double check the service files were purged or disabled and reboot to test.


Thanks for the suggestion. It's not a separate app I can uninstall as it's a kernel module. I have however been able to blacklist it. smile

Offline

#6 2016-12-30 04:27:37

Thorned_Rose
Member
From: Auckland, New Zealand
Registered: 2015-12-30
Posts: 34

Re: Silent shutdown. watchdog: watchdog0: watchdog did not stop!

rdeckard wrote:

Add "nowatchdog" to your kernel parameters. See the new wiki section on watchdogs: https://wiki.archlinux.org/index.php/Im … #Watchdogs

nowatchdog didn't work. However the blacklisting under that wiki entry worked thanks. Simplest method for me was to append this to my bootloader arch.conf options:

modprobe.blacklist=iTCO_wdt

https://wiki.archlinux.org/index.php/Ke … and_line_2

rdeckard wrote:

Additionally, if you are wanting to just suppress the messages you need to lower the loglevel to 1 in your boot parameters. The Wiki gives loglevel=3 as an example in the SIlent Boot article. However, if you lower the loglevel to 1 you are suppressing other possible important messages.

Not really too keen on doing that. But it begs the question, why is a simple reboot/shutdown message which amounts to "Hey, just to let you know, I'm rebooting/shutting down" classed as an error?? loglevel 3 = (KERN_ERR) Non-critical error conditions.

Is there any straight forward way of changing the log level of those messages? Thanks again for your suggestions and help.

Offline

#7 2016-12-30 14:19:19

rdeckard
Member
Registered: 2015-01-28
Posts: 125

Re: Silent shutdown. watchdog: watchdog0: watchdog did not stop!

I'm unsure how to change the level of a message, but the watchdog error message is the one that is level 1 (not the reboot message). Normally I think a watchdog not being able to stop would be considered very important, but because it is part of the normal shutdown in this case I agree that it is simply annoying.

Offline

Board footer

Powered by FluxBB