Date: Fri, 27 Sep 2024 08:09:31 +0200 From: Stephane Rochoy <stephane.rochoy@stormshield.eu> To: mike tancsa <mike@sentex.net> Cc: Chris6 via freebsd-hardware <freebsd-hardware@freebsd.org> Subject: Re: watchdog timer programming Message-ID: <86h6a1egcs.fsf@cthulhu.stephaner.labo.int> In-Reply-To: <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plotbk5b.fsf@cthulhu.stephaner.labo.int> <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> <86plosdv48.fsf@cthulhu.stephaner.labo.int> <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
mike tancsa <mike@sentex.net> writes: > On 9/25/2024 3:13 AM, Stephane Rochoy wrote: >>>>> >>>>> Any idea how to get this hardware working ? >>>> >>>> Do you know if, at least, the pre-timeout is working? >>> >>> How do I check that ? >> >> Using --pretimeout and --pretimeout-action. See watchdogd(8)=20 >> for >> more details. >> > Reverting to the code thats in the tree, I started it up with > > watchdogd --pretimeout 10 --pretimeout-action log -t 15 > > Doesnt seem to work or at least it doesnt make sense to me.=20 > After I > start that up, I see in the logs about 25 seconds after it=20 > starts, but > not always. > > Sep 26 11:31:20 mpki2024 kernel: watchdog pre-timeout,=20 > WD_SOFT_LOG > Sep 26 11:31:20 mpki2024 kernel: Sep 26 11:31:20 pki2024 kernel: > watchdog pre-timeout, WD_SOFT_LOG > > and then doing a kill -9 does nothing :( AFAIK, the pre-timeout should trigger reliably. Weird. --=20 St=C3=A9phane Rochoy O: Stormshield
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86h6a1egcs.fsf>