From owner-freebsd-stable@FreeBSD.ORG  Wed Oct  8 19:07:09 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1EE4F1065690
	for <freebsd-stable@freebsd.org>; Wed,  8 Oct 2008 19:07:09 +0000 (UTC)
	(envelope-from sclark46@earthlink.net)
Received: from elasmtp-junco.atl.sa.earthlink.net
	(elasmtp-junco.atl.sa.earthlink.net [209.86.89.63])
	by mx1.freebsd.org (Postfix) with ESMTP id A85B28FC13
	for <freebsd-stable@freebsd.org>; Wed,  8 Oct 2008 19:07:08 +0000 (UTC)
	(envelope-from sclark46@earthlink.net)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
	b=bZE6h6KNb6UFCvfsVn1b8w0lxztH/QC8PVSJ4XyLPFgyEWDdxHMhidiiA7relqv1;
	h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [208.118.36.229] (helo=joker.seclark.com)
	by elasmtp-junco.atl.sa.earthlink.net with esmtpsa
	(TLSv1:AES256-SHA:256) (Exim 4.67)
	(envelope-from <sclark46@earthlink.net>) id 1KneNI-00052p-2Z
	for freebsd-stable@freebsd.org; Wed, 08 Oct 2008 15:07:08 -0400
Message-ID: <48ED04DA.8050902@earthlink.net>
Date: Wed, 08 Oct 2008 15:07:06 -0400
From: Stephen Clark <sclark46@earthlink.net>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: FreeBSD Stable <freebsd-stable@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec79b4eac57fe25ce350cac1514c41cd37a3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 208.118.36.229
Subject: 6.3-p5 watchdog timer not being disabled
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sclark46@earthlink.net
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Oct 2008 19:07:09 -0000

Hello List,

We have 2 different platforms that we are trying to use the watchdog timer and 
watchdogd program on. One is a Soekris 5501:
CPU: Geode(TM) Integrated Processor by AMD PCS (433.25-MHz 586-class CPU)
   Origin = "AuthenticAMD"  Id = 0x5a2  Stepping = 2
   Features=0x88a93d<FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CLFLUSH,MMX>
   AMD Features=0xc0400000<MMX+,3DNow!+,3DNow!>

The other is a:
CPU: VIA C3 Nehemiah+RNG (1002.28-MHz 686-class CPU)
   Origin = "CentaurHauls"  Id = 0x694  Stepping = 4
   Features=0x380b03d<FPU,DE,PSE,TSC,MSR,MTRR,PGE,CMOV,MMX,FXSR,SSE>

According to the manpage on watchdogd if is killed with either SIGTERM
or SIGINT it is suppose to disable the watchdog timer in the kernel so
the system won't reboot.

On both of the above platforms this does not work and the platforms
reboot when watchdogd is killed with a kill pid,
after the timeout value (-t) that had been specified to watchdogd
when starting it has elapsed.

Am I misunderstanding how this is suppose to work?

Thanks for the elucidation,
Steve


-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)