Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
old_product:odroid-xu4:application_note:software:linux_watchdog [2017/08/23 11:20]
luke.go [Test Watchdog module]
old_product:odroid-xu4:application_note:software:linux_watchdog [2017/10/19 15:20] (current)
luke.go ↷ Page moved from odroid-xu4:application_note:software:linux_watchdog to old_product:odroid-xu4:application_note:software:linux_watchdog
Line 15: Line 15:
  
  
-**Note that the watchdog driver is available in the Kernel update 3.10.82-52 or higher.**\\+**Note that the watchdog driver is available in the Kernel update 3.10.82 ​/ 4.9.51 ​or higher.**\\
 <code bash target> <code bash target>
 odroid@odroid:​~$ uname -a odroid@odroid:​~$ uname -a
Line 143: Line 143:
  
 ===== Start Watchdog Service and Verify ====== ===== Start Watchdog Service and Verify ======
-Watchdog service somehow doesn'​t start automatically. For now if the service doesn'​t start, it can be started with small HACK. 
  
 +**on Ubuntu 14.04.x enable watchdog service status**
 +
 +In order to start service we need to append /​etc/​rc.local
 +service watchdog restart
 +Watchdog service somehow doesn'​t start automatically. For now if the service doesn'​t start, it can be started with small HACK.
 <code bash target> <code bash target>
 root@odroidxu4m:​~#​ cat /​etc/​rc.local root@odroidxu4m:​~#​ cat /​etc/​rc.local
Line 163: Line 167:
  
 exit 0 exit 0
 +</​code>​
 +
 +**on Ubuntu 16.04.x enable watchdog service status**
 +<code bash target>
 +sudo systemctl enable watchdog
 +sudo systemctl start watchdog
 </​code>​ </​code>​
  
Line 187: Line 197:
   Aug 28 10:48:43 odroidxu4m watchdog[4738]:​ current load is 0 0 0   Aug 28 10:48:43 odroidxu4m watchdog[4738]:​ current load is 0 0 0
   Aug 28 10:48:43 odroidxu4m watchdog[4738]:​ was able to ping process 2033 (/​var/​run/​rsyslogd.pid).   Aug 28 10:48:43 odroidxu4m watchdog[4738]:​ was able to ping process 2033 (/​var/​run/​rsyslogd.pid).
 +</​code>​
 +
 +Once the watchdog demon is configured it tries to continuously reset the watchdog timer. When/if it fails to do it (because of unresponsive system), the timer will expire and the board will reboot.
 +
 +Another way to test watchdog device is killing the watchdog demon after it has started.
 +<code bash target>
 +root@odroid64:​~#​
 +root@odroid64:​~#​ pkill -9 watchdog ​
 </​code>​ </​code>​