Date: Fri, 1 Nov 2013 03:11:29 +0800 From: Jia-Shiun Li <jiashiun@gmail.com> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, Andreas Schwarz <freebsd.asc@strcmp.org> Subject: Re: raspberry pi BCM2708 hardware watchdog Message-ID: <CAHNYxxM8MYZRBFvf3cSGB=MOM-CLMOwudJMWdzb-UwAvXK4r%2Bg@mail.gmail.com> In-Reply-To: <F4029D36-8C55-4617-A429-0C5A3DA31C63@bluezbox.com> References: <43584768717.406e8ebb@mail.schwarzes.net> <F4029D36-8C55-4617-A429-0C5A3DA31C63@bluezbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 22, 2013 at 1:24 PM, Oleksandr Tymoshenko <gonzo@bluezbox.com> wrote: > > Watchdog was used for rebooting device only. I've just committed support for > actual watchdog function: http://svnweb.freebsd.org/changeset/base/256871 > Hi, I tried playing the watchdog for a while, but it does not seem to be set correct timeout. I tried to set timeout to 120 seconds to test with the following command, but get immediate reset after around 1~2 seconds: ---8<--- # watchdogd --debug -t 120 --pretimeout 15 --pretimeout-action log,printf -e 'sleep 60' -w shifted 137438953472 seconds_to_pow2ns: seconds: 120, ns 120000000000, power 37 Timeout for -t is 2^37 nanoseconds (in: 120 sec -> out: 137 sec 438953472 ns -> 13745 ticks) Timeout is 2^37 nanoseconds ---8<--- but if I omit the -e command, rpi will keep running and the watchdog hardware seems correctly being kicked by watchdogd. If I directly test with watchdog -d -t 120 it also reboots almost immediately. It there something wrong or did I misunderstand it? I am running FreeBSD raspberry-pi 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r257094: Sat Oct 26 00:16:37 CST 2013 jsli@4cbsd:/rpi/obj/arm.armv6/usr/src/sys/RPI-B arm Regards, Jia-Shiun.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHNYxxM8MYZRBFvf3cSGB=MOM-CLMOwudJMWdzb-UwAvXK4r%2Bg>