From owner-freebsd-questions@FreeBSD.ORG Tue May 10 03:30:49 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F2AE16A4ED for ; Tue, 10 May 2005 03:30:49 +0000 (GMT) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21D5E43D2D for ; Tue, 10 May 2005 03:30:49 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 87222C8DC41 for ; Mon, 9 May 2005 23:30:47 -0400 (EDT) X-Sasl-enc: SN6B4RS3JdADPwMqCW0nRxV6ZZYr0I5HMYm2T0Ni86l1 1115695846 Received: from gumby.localhost (dsl-80-41-65-242.access.as9105.com [80.41.65.242]) by frontend3.messagingengine.com (Postfix) with ESMTP id 127DE84 for ; Mon, 9 May 2005 23:30:45 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Tue, 10 May 2005 04:30:15 +0100 User-Agent: KMail/1.8 References: <5EEBE9C3C61D1142994C6B620C51E847110A73@depot.weblinkmo.com> <44hdhgh5nx.fsf@be-well.ilk.org> <20050507010038.GH9865@tikitechnologies.com> In-Reply-To: <20050507010038.GH9865@tikitechnologies.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505100430.15798.list-freebsd-2004@morbius.sent.com> Subject: Re: 5 day lockup on Densitron X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2005 03:30:49 -0000 On Saturday 07 May 2005 02:00, Clifton Royston wrote: > What you describe > could conceivably be the result of a special counter or RTC chip > running as a "watchdog timer" with a count-down from boot time, and > generating some kind of special interrupt when that countdown reaches > 0. Watchdog devices are sometimes set up to require the application > software to "stroke" the timer periodically (reset it in software) with > the intent to force a reset of the system (usually a reboot) after > such-and-such a period of time if not stroked. Watchdog timeouts are typically a fraction of a minute, a 5 day watchdog timeout is very unlikely.