From 1473ef124e89c1651a7b24bcd6a7519ebc5941f5 Mon Sep 17 00:00:00 2001 From: Yacine Belkadi Date: Wed, 4 Apr 2012 09:47:26 +0200 Subject: cleo/app/fw_wd: identify resets due to firmware watchdog, refs #3051 When the firmware watchdog complains, fw_wd may be configured to reboot. The problem is that "/proc/reset_cause" will say it was due to software reset. So there is no distinction between 1) a soft reset and 2) a soft reset due to the complain of the firmware watchdog. With this commit, fw_wd informs that the real reason for the reset is the firmware watchdog. --- cleopatre/application/fw_wd/fwwatchd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'cleopatre/application/fw_wd') diff --git a/cleopatre/application/fw_wd/fwwatchd b/cleopatre/application/fw_wd/fwwatchd index 1c8d743ce5..add3a5c2a1 100755 --- a/cleopatre/application/fw_wd/fwwatchd +++ b/cleopatre/application/fw_wd/fwwatchd @@ -76,6 +76,6 @@ while true; do fw_wd_pid=$! wait $fw_wd_pid || { kill $fw_wd_pid 2>/dev/null; exit 1; } get_trace - { test $REBOOT = true && reboot; } || \ + { test $REBOOT = true && { echo "watchdog" > /proc/reset_cause; reboot; } } || \ exit 1 done -- cgit v1.2.3