From owner-freebsd-hackers@freebsd.org  Fri Nov  6 19:49:31 2020
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id E839D2D0248
 for <freebsd-hackers@mailman.nyi.freebsd.org>;
 Fri,  6 Nov 2020 19:49:31 +0000 (UTC)
 (envelope-from phk@critter.freebsd.dk)
Received: from s2gw.ddhf.dk (s2gw.ddhf.dk [130.226.214.244])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4CSWDq5ZCWz4gkn;
 Fri,  6 Nov 2020 19:49:31 +0000 (UTC)
 (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.55.3])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by s2gw.ddhf.dk (Postfix) with ESMTPS id CC4D6C3F3A;
 Fri,  6 Nov 2020 19:49:15 +0000 (UTC)
Received: (from phk@localhost)
 by critter.freebsd.dk (8.16.1/8.16.1/Submit) id 0A6JnUxR020509;
 Fri, 6 Nov 2020 19:49:30 GMT (envelope-from phk)
To: Ravi Pokala <rpokala@freebsd.org>
cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
Subject: Re: Have trick, not sure where to document...
In-reply-to: <9498D30F-4FDE-40BE-9941-B7C2DBD6E9DA@panasas.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <9498D30F-4FDE-40BE-9941-B7C2DBD6E9DA@panasas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20507.1604692170.1@critter.freebsd.dk>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 06 Nov 2020 19:49:30 +0000
Message-ID: <20508.1604692170@critter.freebsd.dk>
X-Rspamd-Queue-Id: 4CSWDq5ZCWz4gkn
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-4.00 / 15.00];
	 REPLY(-4.00)[]
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2020 19:49:32 -0000

--------
Ravi Pokala writes:

> If the system has IPMI, there are ways to configure it such that it will=
 enable the watchdog during POST, then disable it when it =

> hands off to the OS. At which time, of course, the OS can re-enable it.

It does not.

I specifically do *not* want it to turn the watchdog off when handing
to the OS, I want to catch problems that cause hanging during boot,
so that I, with suitable patience (or automation), can catch it
next time it resets.

-- =

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    =

Never attribute to malice what can adequately be explained by incompetence=
.