From owner-freebsd-arch Sat Nov 16 1: 6:17 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB2A437B401 for ; Sat, 16 Nov 2002 01:06:16 -0800 (PST) Received: from critter.freebsd.dk (host30-212.bsdcon.customer.bit.nl [213.136.30.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C5F743E91 for ; Sat, 16 Nov 2002 01:06:15 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gAG95YN3005012; Sat, 16 Nov 2002 10:05:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Jeff Roberson Cc: arch@FreeBSD.ORG Subject: Re: Software Watchdog In-Reply-To: Your message of "Fri, 15 Nov 2002 19:21:08 EST." <20021115191632.U22491-100000@mail.chesapeake.net> Date: Sat, 16 Nov 2002 10:05:34 +0100 Message-ID: <5011.1037437534@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021115191632.U22491-100000@mail.chesapeake.net>, Jeff Roberson wr ites: >Sean Kelly has implemented a software watchdog based on input from myself >and Peter. This works through a simple watcdog daemon that checks in with >the kernel every so often. The kernel complains via hardclock() if the >watchdog times out. This will be very useful for debugging hard lockups >because hardclock() comes in through a fast intr. There are few things >that will stop hardclock() from firing. Does it have hooks for supporting hardware watchdogs ? -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message