| 14:34 | topi`_ | any watchdog experts here? I enabled the imx2+ WD in hummingboard via installing/running watchdog.service which opens /dev/watchdog and pets it |
| 14:34 | topi`_ | but I tried to kill that service and let the system die, but it did not die |
| 14:34 | topi`_ | watchdog: watchdog0: nowayout prevents watchdog being stopped! |
| 14:35 | topi`_ | watchdog: watchdog0: watchdog did not stop! |
| 14:35 | topi`_ | then I waited, and waited... and nothing happened :( |
| 14:46 | vpeter | topi`_: read http://trac.gateworks.com/wiki/watchdog |
| 14:46 | vpeter | but i'm no expert :-) |
| 14:55 | topi`_ | thanks for the page |
| 14:55 | topi`_ | it doesn't explain why my watchdog0 doesn't reset the board when I kill the wd daemon :( |
| 14:56 | topi`_ | maybe there's still *someone* writing to watchdog0... |
| 15:03 | vpeter | I think you didn't kill it. |
| 15:04 | vpeter | Or maybe time was set longer than you wait. |
| 15:22 | Artox | topi`: doesn't u-boot have to enable the watchdog? |
| 16:11 | topi` | Artox: probably so, but if I activate "watchdog" in the userspace, it writes to /dev/watchdog and hence starts the hadrware WD |
| 16:12 | topi` | I need to write a program to query the wd device by ioctl's |
| 16:20 | topi` | it seems systemd's ShutdownWatchdogSec=xx option is not working. |
| 16:21 | topi` | I set it to 60, but now the reboot process is stuck at the line "Reached target Shutdown" and nothing happens... |
| 16:21 | topi` | systemd should have programmed the watchdog to reset after 60s |
| 16:25 | topi` | this is odd - after the systemd's reboot process gets stuck, also forcing a reboot via the SysRq key ends up rebooting, UBOOT appears, loads kernel, then NOTHING on the serial console |
| 16:25 | topi` | "Starting kernel..." |
| 16:25 | topi` | Loaded imx6q-hummingboard2-som-v15.dtb |
| 16:25 | topi` | it loads the correct .dtb file... |