Date: Thu, 26 Sep 2024 11:56:59 -0400 From: mike tancsa <mike@sentex.net> To: Chris6 via freebsd-hardware <freebsd-hardware@freebsd.org> Subject: Re: watchdog timer programming Message-ID: <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> In-Reply-To: <86plosdv48.fsf@cthulhu.stephaner.labo.int> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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) 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. After I start that up, I see in the logs about 25 seconds after it starts, but not always. Sep 26 11:31:20 mpki2024 kernel: watchdog pre-timeout, 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 :( ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78e9461c-b93d-403f-b3a1-3568548b9283>