Per Linda Knippers (HP) :
Why are you blacklisting the watchdog timers? It seems like if corosync wants to use them, which is why it would open /dev/watchdog, then there's either a corosync bug or there's something in the configuration that isn't right. Is anyone looking into that?
For cluster configurations, you probably really do want a watchdog so that hung systems can crash, reboot and rejoin the cluster.
And what about non-corosync configurations? Other distros run the watchdog timers just fine. Blacklisting the watchdog timer just hides underlying problems.
Per Linda Knippers (HP) :
Why are you blacklisting the watchdog timers? It seems like if corosync wants to use them, which is why it would open /dev/watchdog, then there's either a corosync bug or there's something in the configuration that isn't right. Is anyone looking into that?
For cluster configurations, you probably really do want a watchdog so that hung systems can crash, reboot and rejoin the cluster.
And what about non-corosync configurations? Other distros run the watchdog timers just fine. Blacklisting the watchdog timer just hides underlying problems.