How to correctly configure Debian watchdog daemon for BIOS Watch Dog?
Clash Royale CLAN TAG#URR8PPP
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:
- Change BIOS "Watch Dog Function" from Disabled to Enabled.
- 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?
debian bios watchdog
asked Feb 7 '13 at 11:30
Pro Backup
1,98862957
add a comment |
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:
- Change BIOS "Watch Dog Function" from Disabled to Enabled.
- 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?
debian bios watchdog
asked Feb 7 '13 at 11:30
Pro Backup
1,98862957
1
Removed thewatchtag becausewatchandwatchdogare very different.
– a CVn
Feb 7 '13 at 11:37
add a comment |
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:
- Change BIOS "Watch Dog Function" from Disabled to Enabled.
- 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?
debian bios watchdog
asked Feb 7 '13 at 11:30
Pro Backup
1,98862957
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:
- Change BIOS "Watch Dog Function" from Disabled to Enabled.
- 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?
debian bios watchdog
debian bios watchdog
asked Feb 7 '13 at 11:30
Pro Backup
1,98862957
asked Feb 7 '13 at 11:30
Pro Backup
1,98862957
edited Feb 7 '13 at 11:39
asked Feb 7 '13 at 11:30
Pro Backup
1,98862957
asked Feb 7 '13 at 11:30
Pro Backup
1,98862957
asked Feb 7 '13 at 11:30
Pro Backup
1,98862957
1,98862957
1
Removed thewatchtag becausewatchandwatchdogare very different.
– a CVn
Feb 7 '13 at 11:37
add a comment |
1
Removed thewatchtag becausewatchandwatchdogare very different.
– a CVn
Feb 7 '13 at 11:37
1
1
Removed the
watch tag because watch and watchdog are very different.– a CVn
Feb 7 '13 at 11:37
Removed the
watch tag because watch and watchdog are very different.– a CVn
Feb 7 '13 at 11:37
add a comment |
1 Answer
1
active
oldest
votes
1. Load hardware module
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). Note that iTCO_wdt might require some other modules like i2c-i801, i2c-smbus to do its magic. Try using modprobe iTCO_wdt to load that module and see if it is accepted.
Success looks like:
iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
Failure shows nothing after:
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Also check syslog. Otherwise check out the IPMI tools as they include a watchdog driver.
2. Edit /etc/watchdog.conf
Secondly, you need to edit the watchdog configuration file, like # nano /etc/watchdog.conf.
3. Un-comment watchdog-device = ...
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.
edited Dec 24 '18 at 18:29
Pro Backup
1,98862957
answered Sep 4 '13 at 16:53
Paul Crawford
17626
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f64057%2fhow-to-correctly-configure-debian-watchdog-daemon-for-bios-watch-dog%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1. Load hardware module
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). Note that iTCO_wdt might require some other modules like i2c-i801, i2c-smbus to do its magic. Try using modprobe iTCO_wdt to load that module and see if it is accepted.
Success looks like:
iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
Failure shows nothing after:
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Also check syslog. Otherwise check out the IPMI tools as they include a watchdog driver.
2. Edit /etc/watchdog.conf
Secondly, you need to edit the watchdog configuration file, like # nano /etc/watchdog.conf.
3. Un-comment watchdog-device = ...
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.
edited Dec 24 '18 at 18:29
Pro Backup
1,98862957
answered Sep 4 '13 at 16:53
Paul Crawford
17626
add a comment |
1. Load hardware module
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). Note that iTCO_wdt might require some other modules like i2c-i801, i2c-smbus to do its magic. Try using modprobe iTCO_wdt to load that module and see if it is accepted.
Success looks like:
iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
Failure shows nothing after:
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Also check syslog. Otherwise check out the IPMI tools as they include a watchdog driver.
2. Edit /etc/watchdog.conf
Secondly, you need to edit the watchdog configuration file, like # nano /etc/watchdog.conf.
3. Un-comment watchdog-device = ...
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.
edited Dec 24 '18 at 18:29
Pro Backup
1,98862957
answered Sep 4 '13 at 16:53
Paul Crawford
17626
add a comment |
1. Load hardware module
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). Note that iTCO_wdt might require some other modules like i2c-i801, i2c-smbus to do its magic. Try using modprobe iTCO_wdt to load that module and see if it is accepted.
Success looks like:
iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
Failure shows nothing after:
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Also check syslog. Otherwise check out the IPMI tools as they include a watchdog driver.
2. Edit /etc/watchdog.conf
Secondly, you need to edit the watchdog configuration file, like # nano /etc/watchdog.conf.
3. Un-comment watchdog-device = ...
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.
edited Dec 24 '18 at 18:29
Pro Backup
1,98862957
answered Sep 4 '13 at 16:53
Paul Crawford
17626
1. Load hardware module
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). Note that iTCO_wdt might require some other modules like i2c-i801, i2c-smbus to do its magic. Try using modprobe iTCO_wdt to load that module and see if it is accepted.
Success looks like:
iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
Failure shows nothing after:
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Also check syslog. Otherwise check out the IPMI tools as they include a watchdog driver.
2. Edit /etc/watchdog.conf
Secondly, you need to edit the watchdog configuration file, like # nano /etc/watchdog.conf.
3. Un-comment watchdog-device = ...
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.
edited Dec 24 '18 at 18:29
Pro Backup
1,98862957
answered Sep 4 '13 at 16:53
Paul Crawford
17626
edited Dec 24 '18 at 18:29
Pro Backup
1,98862957
edited Dec 24 '18 at 18:29
Pro Backup
1,98862957
edited Dec 24 '18 at 18:29
Pro Backup
1,98862957
1,98862957
answered Sep 4 '13 at 16:53
Paul Crawford
17626
answered Sep 4 '13 at 16:53
Paul Crawford
17626
answered Sep 4 '13 at 16:53
Paul Crawford
17626
17626
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f64057%2fhow-to-correctly-configure-debian-watchdog-daemon-for-bios-watch-dog%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Removed the
watchtag becausewatchandwatchdogare very different.– a CVn
Feb 7 '13 at 11:37