Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Aug 2021 19:45:29 -0400
From:      Alexander Motin <mav@FreeBSD.org>
To:        mike tancsa <mike@sentex.net>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: ipmi0: Watchdog set returned 0xc0 (releng_13)
Message-ID:  <fc5f879f-91da-c45d-366c-29c721de948e@FreeBSD.org>
In-Reply-To: <2c1ad9db-b92a-d0a8-b2ae-b3ffafc04604@sentex.net>
References:  <c065ff32-719f-ef2e-85b9-d5504a36810f@sentex.net> <51e58d7a-1b33-f7e3-13aa-3be5fee5c826@FreeBSD.org> <2c1ad9db-b92a-d0a8-b2ae-b3ffafc04604@sentex.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 16.08.2021 10:53, mike tancsa wrote:
> One other thing I noticed was that if I boot up without ipmi loaded,
> /dev/fido is there. Does it still see a hardware watchdog somehow, or is
> that pointing to something else ?

As I see in the watchdog driver code, the device is created just on
module load, whenever the hardware present or not.  Actually, if there
is no hardware watchdog, modern kernel should attach a software one.  It
is obviously less reliable, but we successfully use that one in some of
our products.

> I am going to look around for a BIOS update to see if there is some fix

I'd look more for BMC firmware update, not BIOS.  Or both, if available.

-- 
Alexander Motin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fc5f879f-91da-c45d-366c-29c721de948e>