You are not logged in.
Pages: 1
Topic closed
Hello everyone !
I have a strange 'problem' when I reboot my computer :
# reboot
kernel: watchdog watchdog0: watchdog did not stop!
...
Do you think it is normal? It has appeared very recently. After a systemd update (don't remember which one).
Last edited by CEPfister (2012-11-19 07:35:40)
Offline
System up to date?
Switched to systemd?
Installed systemd-sysvcompat?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
What is the flavor of your computer?
What kernel are you running?
What is your boot system (Grub2, Syslinux. etc...)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I am having the same problem, running kernel 3.6.7-1-ck, but the message has been there for a while, also with the stock kernel. I *think* it appeared after changing to systemd. I can't be sure though, as I installed arch with the 8/2012 install medium and immediately changed to systemd.
My computer is a laptop with i5-2450M, optimus, pure systemd and everything up-to-date. Booting with grub2.
I only ever see this message on reboot, never when powering down.
Other than this and some other kernel messages mainly during boot (which seem to be mostly harmless, are known to upstream and should get fixed - someday) everything is working fine.
Offline
I only ever see this message on reboot, never when powering down.
Same thing for me. I know plenty of people that have the exact same issue, but they simply don't care since their computers are still working.
I have a fully updated system with systemd and systemd-sysvcompat. I am using syslinux with kernel 3.6.6-1-ARCH x86_64.
Last edited by CEPfister (2012-11-19 09:24:18)
Offline
Hello everyone !
I have a strange 'problem' when I reboot my computer :
# reboot kernel: watchdog watchdog0: watchdog did not stop! ...
Do you think it is normal? It has appeared very recently. After a systemd update (don't remember which one).
This is perfectly normal. When shutting down, systemd sets a watchdog timeout of 10 minutes (see /etc/systemd/system.conf), then closes the watchdog before executing systemd-shutdown (this is a bit simplified, I can't remember the precise mechanics). As systemd did not stop the watchdog, Linux warns you. This has the effect that if shutdown is not completed within 10 minutes, your hardware watchdog will trigger the specified action.
Offline
This is perfectly normal. When shutting down, systemd sets a watchdog timeout of 10 minutes (see /etc/systemd/system.conf), then closes the watchdog before executing systemd-shutdown (this is a bit simplified, I can't remember the precise mechanics). As systemd did not stop the watchdog, Linux warns you. This has the effect that if shutdown is not completed within 10 minutes, your hardware watchdog will trigger the specified action.
This was quite informative. Thank you.
Last edited by idoit (2013-10-21 10:22:30)
Offline
Forum Etiquette: Old Threads / Necro-Bumping - Closing.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
Pages: 1
Topic closed