http://bugzilla.suse.com/show_bug.cgi?id=1042933
http://bugzilla.suse.com/show_bug.cgi?id=1042933#c28
--- Comment #28 from Jerry Hoemann
(In reply to Jerry Hoemann from comment #26)
Proper programming of a watchdog is a bit of an art form.
That's the nice way to put it.
Note, the ASR is disabled by default, it must be turned on by an application opening /dev/watchdog etc.,. The ASR can later be explicitly disabled after being previously enabled.
So Thomas' example opens /dev/watchdog. How does one disable the ASR? And while we're disabling things, how can one disable the pretimeout too?
This way you'll have the watchdog behave as one expects it to. Just for the sake of the test.
Thanks.
Sorry, I didn't get an email notification on this comment and didn't see your question until I pulled up the bz to review for the other NMI issue I'm looking into. For HPE hpwdt, the ASR is disabled by writing the "magic" close to /dev/watchdog: E.g: echo V > /dev/watchdog. Re-opening /dev/watchdog will start the timer again. The hpwdt driver doesn't separate the pretimeout feature from ASR feature. So there is no way a user can turn off just the pretimeout NMI and leave the ASR feature enabled. Documentation/watchdog/watchdog-api.txt describes in greater detail both the magic close and the pretimeout feature. -- You are receiving this mail because: You are on the CC list for the bug.