From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 16:10:33 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B850E106566C for ; Mon, 17 Jan 2011 16:10:33 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 7214B8FC1D for ; Mon, 17 Jan 2011 16:10:33 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:6d90:8d21:568f:4366] ([IPv6:2607:f3e0:0:4:6d90:8d21:568f:4366]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id p0HGAVZF061595 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 17 Jan 2011 11:10:31 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D3469EF.9030808@sentex.net> Date: Mon, 17 Jan 2011 11:10:23 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Marek Salwerowicz References: <19E3EEDE916642219C40F9DE5C23E1B6@marekdesktop> <4D33AD5B.5040703@sentex.net> <4D3462A2.9050602@sentex.net> <5E7B2EDC7FE74DC786DC226EBB521C36@marekdesktop> In-Reply-To: <5E7B2EDC7FE74DC786DC226EBB521C36@marekdesktop> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: freebsd-current@freebsd.org, soekris-tech@lists.soekris.com Subject: Re: [Soekris] Soekris net5501 - how to use hardware watchdog? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2011 16:10:33 -0000 On 1/17/2011 11:07 AM, Marek Salwerowicz wrote: >>> Hi, >>> Try adding >>> option CPU_SOEKRIS >> >> Sorry, for the 5501 thats >> >> option CPU_GEODE >> >> ---Mike > > I have added both. Is there any possible test to check if watchdog > really does reboot ? > Just start /usr/sbin/watchdogd and then kill the process? Yes, but make sure you do kill -9, not just kill ---Mike