Date: Sat, 16 Nov 2002 10:05:34 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Jeff Roberson <jroberson@chesapeake.net> Cc: arch@FreeBSD.ORG Subject: Re: Software Watchdog Message-ID: <5011.1037437534@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 15 Nov 2002 19:21:08 EST." <20021115191632.U22491-100000@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5011.1037437534>