https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252863
Bug ID: 252863
Summary: ipmi watchdog does not reset after being triggered
Product: Base System
Version: 12.2-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: j...@transactionware.com
On a Supermicro X11SCM-F based system, with the ipmi watchdog enabled, the
watchdog will only trigger once. After the system comes back up after a
watchdog triggered reboot the watchdog is ineffective and no error messages are
printed.
To make the watchdog work again, I have to reset the BMC by disconnecting power
from the system or issuing "ipmicontrol mc reset warm".
Output from "ipmitool mc watchdog get" after a full reset, system and BMC:
Watchdog Timer Use: Reserved (0x00)
Watchdog Timer Is: Stopped
Watchdog Timer Actions: No action (0x00)
Pre-timeout interval: 0 seconds
Timer Expiration Flags: 0x00
Initial Countdown: 0 sec
Present Countdown: 0 sec
Output from "ipmitool mc watchdog get" while the watchdog is running:
Watchdog Timer Use: SMS/OS (0x44)
Watchdog Timer Is: Started/Running
Watchdog Timer Actions: Power Cycle (0x03)
Pre-timeout interval: 120 seconds
Timer Expiration Flags: 0x00
Initial Countdown: 17 sec
Present Countdown: 14 sec
Output from "ipmitool mc watchdog get" after the system has come back up after
the watchdog power cycle:
Watchdog Timer Use: SMS/OS (0x04)
Watchdog Timer Is: Stopped
Watchdog Timer Actions: Power Cycle (0x03)
Pre-timeout interval: 120 seconds
Timer Expiration Flags: 0x10
Initial Countdown: 17 sec
Present Countdown: 0 sec
Attempting to reset the watchdog with "ipmitool mc watchdog reset" fails with
"Reset Watchdog Timer command failed: Node busy".
dmesg for ipmi:
ipmi0: <IPMI System Interface> port 0xca2,0xca3 on acpi0
ipmi0: KCS mode found at io 0xca2 on acpi
ipmi0: IPMI device rev. 1, firmware rev. 1.23, version 2.0, device support mask
0xbf
ipmi0: Number of channels 2
ipmi0: Attached watchdog
ipmi0: Establishing power cycle handler
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
