Timeline for How do I cause a watchdog reset of my embedded Linux device
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 18, 2022 at 9:52 | comment | added | Vladimir Panteleev |
SIGSTOP will be better than SIGKILL when the driver stops the watchdog when the file descriptor gets closed. See the kernel documentation, especially regarding "Magic Close" and CONFIG_WATCHDOG_NOWAYOUT.
|
|
| Oct 2, 2016 at 9:54 | comment | added | Paul Crawford | If killing the watchdog daemon you must use SIGKILL and not the usual SIGTERM which performs an orderly shut-down and so closes the driver. Using SIGSTOP as suggested by @KristofProvost achieves the same goal of preventing the periodic refresh. | |
| Feb 7, 2013 at 15:22 | comment | added | Kristof Provost | Simply killing the watchdog daemon might not be good enough. Depending on how the watchdog device is configured it might disable the watchdog if /dev/watchdog is closed. In that case you can try sending SIGSTOP to your watchdog process instead. | |
| Sep 26, 2011 at 1:20 | vote | accept | Ankur Agarwal | ||
| Sep 24, 2011 at 3:06 | history | answered | Shawn J. Goff | CC BY-SA 3.0 |