Watchdog didn't stop at shutdown

Blacklist the modules in /etc/modeprobe.d/blacklist.conf (create this file if you don’t have it).

On one of my computers, I had to do this.

For example, the watchdogs I had in use were 2 modules, iTCO_wdt and mei_wdt; mei-wdt is part of Intel’s Management Engine Interface. I have blacklisted both; this is what my /etc/modeprobe.d/blacklist.conf looks like:

# disable intel mei (including mei_watchdog)
blacklist mei
blacklist mei_me
blacklist mei_hdcp
blacklist mei_wdt

# Do not load the 'iTCO_wdt' watchdog module on boot.
blacklist iTCO_wdt

That’s for my modules; you’ll want to use the ones that you have instead.

(I’m not familiar with intel_pmc_bxt - you may want to try just blacklisting the 2 iTCO modules first, as I know it is safe to do so)

5 Likes

Found some info on it:

This driver provides support for the PMC (Power Management Controller) on Intel Broxton and Apollo Lake. The PMC is a multi-function device that exposes IPC, General Control Register and P-unit access. In addition this creates devices for iTCO watchdog and telemetry that are part of the PMC.

https://cateee.net/lkddb/web-lkddb/MFD_INTEL_PMC_BXT.html

1 Like

Disabling the iTCO watchdog modules might be all you need, then.

2 Likes

And also this in my case: iTCO_vendor_support. Since with only blocking iTCO_wdt I had still those “error” messages.

2 Likes

We had the same problem :smiling_face_with_three_hearts:

1 Like

I have this done and it works for me:

# disable intel mei (including mei_watchdog)
blacklist intel_pmc_bxt          16384  1 iTCO_wdt
blacklist iTCO_vendor_support    16384  1 iTCO_wdt

# Do not load the 'iTCO_wdt' watchdog module on boot.
blacklist iTCO_wdt

How do I recognize that this might not be necessary with any later kernel version or in other words: is this a permanent solution for the future?

4 Likes

This should continue working, unless there is a major change in the kernel.

Then we’ll have to start all over again :grin:. But I wouldn’t worry about it.

One minor technicality: you didn’t disable intel-mei, but intel_pmc_bxt - it doesn’t really matter, but you might want to change this comment in your blacklist file for future clarity:

4 Likes

This file shouldn’t be touched by kernel updates/installations.

2 Likes

Ok, thanks @anon3337769 @pebcak :+1:t2:

3 Likes

I’ve never even thought to look into it. I always think “awesome my watch dog is on guard while I’m away from my computer”

I’ll probably leave it and not fix it because of that.

3 Likes

The problem is, with some people, on some systems, it hangs for 90 seconds or so at reboot or shutdown.

You can shorten the timer to a few seconds, or go deep-diving to try and figure out what is misconfigured, but since watchdogs aren’t particularly useful for personal computers, I find it more efficient to simply disable them.

2 Likes

The topic has been up before, and there is a solution here:

3 Likes

The nowatchdog boot parameter doesn’t always work, though. Sometimes you have to blacklist the modules.

4 Likes

It certainly is.

Old topic but one that has finally fixed the issue that has plagued me …like forever. It stalled shutdowns on both my desktop and laptop. Just a :raised_hands:, and maybe a :+1: and a couple of :kissing_heart: to all those above for the fixes. Thank you.

2 Likes

I run this command but it gives no output even though watchdog not stopped messages appear when I shut down system.

sorry, I didn’r read the whole thread, simply do this.

Blacklist the modules in /etc/modeprobe.d/blacklist.conf (create this file if you don’t have it).

To disable watchdog timers (both software and hardware), append nowatchdog to your boot parameters.

sudo nano /etc/modprobe.d/blacklist.conf

# disable intel mei (including mei_watchdog)
blacklist intel_pmc_bxt          16384  1 iTCO_wdt
blacklist iTCO_vendor_support    16384  1 iTCO_wdt

# Do not load the 'iTCO_wdt' watchdog module on boot.
blacklist iTCO_wdt
2 Likes

I don’t have Intel chip it’s AMD, does that make a difference?

This is what I see at every shutdown…

Screenshot_20210620_150949

I do not know, just try it :wink:

1 Like

I was getting those as well. I remembered something I used to do to fix it but had to dig into my notebook. Try this:

Make this file:
sudo nano /etc/modprobe.d/sp5100_tco.conf
Put this in the file:
blacklist sp5100_tco
hit ctrl+o to write
enter to save
ctrl+x to exit
Then
sytemctrl reboot

I don’t see those messages anymore. As well as journal warnings.

If this fixes it for you I will come back and clean this thread up and make a new one as the original has been marked solved. Some are going to say there is a better way to do this and they are right i just can’t find it anymore. If it works it works!