Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Supermicro main boards contain a BIOS feature named "Watch Dog Function". Having Debian 6.0.6 with kernel "Linux debian 2.6.32-5-amd64 #1 SMP" we did:

  1. Change BIOS "Watch Dog Function" from Disabled to Enabled.
  2. Install the package watchdog (# apt-get install watchdog)

Expected: that would be all for the watchdog function to be correctly installed.

Result: system reboots every (roughly) 5 minutes.

Change BIOS "Watch Dog Function" from Enabled to Disabled fixes the undesired reboots.

The boot process seems to correctly enable the watchdog daemon. At least console displays (when BIOS Watch Dog is disabled):

Starting watchdog keepalive daemon: wd_keepalive.
Stopping watchdog keepalive daemon....
Starting watchdog daemon....

And on reboot this output is generated:

INIT: SUsing makefile-style concurrent boot in runlevel 6.
Stopping watchdog daemon....
Starting watchdog keepalive daemon....

What else need to be done to configure the BIOS watch dog function and Linux OS watchdog daemon to work together correctly?

share|improve this question
Removed the watch tag because watch and watchdog are very different. – Michael Kjörling Feb 7 '13 at 11:37

Firstly, in order to actually 'feed' the watchdog, you need to have the watchdog hardware module loaded. This may not happen automatically as most watchdog drivers are blacklisted in case there is no watchdog daemon (e.g. in /etc/modprobe.d/blacklist-watchdog.conf on an Ubuntu/Debian system). Check to see if /dev/watchdog (or similar) has appeared, as that would imply the module has been loaded.

I don't know what the Supermicro board uses, but it may be the Intel TCO driver (iTCO_wdt). Try using modprobe to load that module and see if it is accepted (also check syslog). Otherwise check out the IPMI tools as they include a watchdog driver.

Secondly, you need to edit the /etc/watchdog.conf file to un-comment and so actually use the /dev/watchdog device access to the module. Otherwise the watchdog will not use the hardware and rely only on its internal code to soft-reboot a broken machine (which is not so useful).

Again, on starting the watchdog daemon look for messages in syslog about it starting and what hardware module it has found.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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