You are not logged in.
Hi!
I have a motherboard with a hardware watchdog and the system loads iTCO_wdt automatically. When I enable the watchdog service the system still gets reset after a while and no /dev/watchdog or similar shows up nor can I find any information on how to solve this.
The kernel loads these releated modules:
iTCO_wdt 16384 0
iTCO_vendor_support 16384 1 iTCO_wdt
The watchdog service tries to read/write to /dev/watchdog but it fails (no such file, errno = 2). I keep it disabled in the UEFI setup but I want to use it. My machine has hanged a few times. I want to use the watchdog feature so I know that the system won't be waiting for to get home.
Thanks in advance!
Offline
What is MoBo brand,model & revision ?
Are you running latest firmware ?
what package does the watchdog service come from and what is in it that file ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
What is MoBo brand,model & revision ?
Are you running latest firmware ?
what package does the watchdog service come from and what is in it that file ?
It's an ASRock D2750D4I. It's running the latest firmware.
The watchdog has worked for me before when I compiled Linux myself, but that was quite a few years ago.
The package is called "watchdog".
The watchdog service configuration (/etc/watchdog.conf) contains the following:
#ping = 172.31.14.1
#ping = 172.26.1.255
#interface = eth0
#file = /var/log/messages
#change = 1407
# Uncomment to enable test. Setting one of these values to '0' disables it.
# These values will hopefully never reboot your machine during normal use
# (if your machine is really hung, the loadavg will go much higher than 25)
#max-load-1 = 24
#max-load-5 = 18
#max-load-15 = 12
# Note that this is the number of pages!
# To get the real size, check how large the pagesize is on your machine.
#min-memory = 1
#allocatable-memory = 1
#repair-binary = /usr/sbin/repair
#repair-timeout =
#test-binary =
#test-timeout =
watchdog-device = /dev/watchdog
# Defaults compiled into the binary
#temperature-device =
#max-temperature = 120
# Defaults compiled into the binary
#admin = root
#interval = 1
#logtick = 1
#log-dir = /var/log/watchdog
# This greatly decreases the chance that watchdog won't be scheduled before
# your machine is really loaded
realtime = yes
priority = 1
# Check if rsyslogd is still running by enabling the following line
#pidfile = /var/run/rsyslogd.pid
Last edited by SaltySockets (2016-08-29 21:30:37)
Offline
What are the output of lsmod | grep ipmi ?
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
What are the output of lsmod | grep ipmi ?
$ lsmod | grep ipmi
ipmi_ssif 24576 0
ipmi_si 53248 0
ipmi_msghandler 40960 2 ipmi_ssif,ipmi_si
Offline
I keep it disabled in the UEFI setup but I want to use it.
So, did you enable it?
BTW -- that the ipmi stuff is loading is a good thing https://en.wikipedia.org/wiki/Intellige … _Interface
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
SaltySockets wrote:I keep it disabled in the UEFI setup but I want to use it.
So, did you enable it?
BTW -- that the ipmi stuff is loading is a good thing https://en.wikipedia.org/wiki/Intellige … _Interface
If I enable it then the system will reset. The device should still visible but not reset the system when the timer reaches 0. The iTCO_wdt module is loaded automatically even when the watchdog is disabled. I tried to get it up and running earlier today but it kept resetting the machine. So something isn't talking with the watchdog device, wherever it is hiding.
Yeah, I use the IPMI to administer the UEFI and other things not availible through SSH. I have no monitor or keyboard connected to it. I also installed Arch by mounting the ISO through IPMI. BMC's are lovely!
Offline
Re: IPMI and BMCs, make sure you understand the consequences.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Unfortunately, that is about all I can offer on the subject. I don't use watchdogs myself on my general purpose machines. I do, of course, you them on embedded systems.
The only other possibility is that your hardware needs one of the modules not enabled in the stock kernel. There are a couple of them:
ewaller@turing ~ 1019 %zcat /proc/config.gz| grep WATCHDOG | grep "not set"
# CONFIG_DPM_WATCHDOG is not set
# CONFIG_WATCHDOG_NOWAYOUT is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_RN5T618_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_WQ_WATCHDOG is not set
ewaller@turing ~ 1020 %
Perhaps building a kernel with those enabled?
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
$ ls /dev/watchdog*
/dev/watchdog /dev/watchdog0
$ dmesg |grep iTCO_wdt
[ 7.084376] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 7.084422] iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x1060)
[ 7.084699] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Does it look the same on your machine?
Offline
I think the OP stated that there are no appropriate dev nodes.
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
So I updated the BMC so now both the UEFI and BMC are up to date. I've reset both to factory defaults and made the changes that I want.
The iTCO modules say this regardless if I set the Watchdog to Disable or Reset:
kernel: iTCO_vendor_support: vendor-support=0
kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
kernel: iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS
It even resets when I'm in the UEFI firmware, looking around.
Does it sound like a bug in the firmware? (board: ASRock Rack C2750D4I)
Offline