summaryrefslogtreecommitdiff
path: root/cleopatre/application
diff options
context:
space:
mode:
authorYacine Belkadi2012-04-04 09:47:26 +0200
committerYacine Belkadi2012-05-03 09:31:53 +0200
commit1473ef124e89c1651a7b24bcd6a7519ebc5941f5 (patch)
tree21c46b4ea03b77ebfc6d0fa82cdafc4e824acdc4 /cleopatre/application
parentf4f9d13c8daf76c54a73a0842891a67034aa6be2 (diff)
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.
Diffstat (limited to 'cleopatre/application')
-rwxr-xr-xcleopatre/application/fw_wd/fwwatchd2
1 files changed, 1 insertions, 1 deletions
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