15

At shutdown I often get the message

watchdog did not stop!

and then the laptop freezes after few other lines without shutting down.

Any idea on how to fix this? Recently it happened very often, usually when the laptop was powered on for some time.

I am using Debian 8 on an Asus UX32LA

I found this systemd file (it shows a conflict with the shutdown.target), if it may help. My impression is that the problem depends on some issue coming from me trying to fix the backlight (which actually only works with the grub paramenter "acpi_osi=" )

[Unit]
Description=Load/Save Screen Backlight Brightness of %i
Documentation=man:systemd-backlight@.service(8)
DefaultDependencies=no
RequiresMountsFor=/var/lib/systemd/backlight
Conflicts=shutdown.target  
After=systemd-readahead-collect.service systemd-readahead-replay.service     systemd-remount-fs.service
Before=sysinit.target shutdown.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/lib/systemd/systemd-backlight load %i
ExecStop=/lib/systemd/systemd-backlight save %i
  • 1
    Can you try removing "rhgb quiet" from boot cmdline and then see what happens? – shubham Dec 16 '15 at 7:26
  • Exactly what I was going to suggest. "rhgb quiet" suppresses messages at boot/shutdown that could be quite useful here. – Tim S. Jan 22 '16 at 20:36
  • there is no "rhgb quiet" in /etc/default/grub (and grub is updated) – Reyx_0 Jan 24 '16 at 19:13
14

The watchdog did not stop! line is normal behavior. systemd sets a "hardware watchdog" timer as a failsafe, to ensure that if the normal shutdown process freezes/fails that the computer will still shutdown after the specified period of time. This time period is defined in the variable ShutdownWatchdogSec= in the file /etc/systemd/system.conf. Here is the description from the docs:

RuntimeWatchdogSec=, ShutdownWatchdogSec=

Configure the hardware watchdog at runtime and at reboot. Takes a timeout value in seconds (or in other time units if suffixed with "ms", "min", "h", "d", "w"). If RuntimeWatchdogSec= is set to a non-zero value, the watchdog hardware (/dev/watchdog) will be programmed to automatically reboot the system if it is not contacted within the specified timeout interval. The system manager will ensure to contact it at least once in half the specified timeout interval. This feature requires a hardware watchdog device to be present, as it is commonly the case in embedded and server systems. Not all hardware watchdogs allow configuration of the reboot timeout, in which case the closest available timeout is picked. ShutdownWatchdogSec= may be used to configure the hardware watchdog when the system is asked to reboot. It works as a safety net to ensure that the reboot takes place even if a clean reboot attempt times out. By default RuntimeWatchdogSec= defaults to 0 (off), and ShutdownWatchdogSec= to 10min. These settings have no effect if a hardware watchdog is not available.

It sounds likely, as you indicated, that your actual problem is related to changing ACPI settings. The answers on this Debian forum thread suggest the following:

1) Edit the file at /etc/default/grub and edit the GRUB_CMDLINE_LINUX line to look like this: GRUB_CMDLINE_LINUX="reboot=bios"

2) run: update-grub

If reboot=bios doesn't work, they suggest retrying with reboot=acpi

Do either of these work for you?

  • I implemented the changes you suggested, and let you know soon. Thanks – Reyx_0 Dec 22 '15 at 21:59
  • unfortunately it does not work. and I suspect that the issue is related to this other problem I also have (i.e. laptop sporadically freezes on suspend): see bugzilla.kernel.org/show_bug.cgi?id=102091 – Reyx_0 Jan 24 '16 at 19:11
  • I have found that /sbin/shutdown -r now works instead of shutdown -r now or reboot. – xinthose Jan 17 '18 at 22:15
1

I am on a MIO single board computer with the same problem: sudo reboot or [CTRL]+[ALT]+[DEL] leads to hanging at

watchdog did not stop

None of the above worked for me, but thankfully a combination of them did the job:

  1. Use GRUB_CMDLINE_LINUX="reboot=bios" (reboot=acpi did not work for me)

  2. Use systemctl reboot -i, to successfully reboot the system. (link)

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.