From owner-freebsd-stable@FreeBSD.ORG Fri May 14 14:15:17 2010 Return-Path: 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 A321D106566C for ; Fri, 14 May 2010 14:15:17 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 5285F8FC25 for ; Fri, 14 May 2010 14:15:16 +0000 (UTC) Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta13.westchester.pa.mail.comcast.net with comcast id HNHT1e0011vXlb85DSFHlH; Fri, 14 May 2010 14:15:17 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta17.westchester.pa.mail.comcast.net with comcast id HSFF1e0073S48mS3dSFG1a; Fri, 14 May 2010 14:15:16 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 1EED49B419; Fri, 14 May 2010 07:15:14 -0700 (PDT) Date: Fri, 14 May 2010 07:15:14 -0700 From: Jeremy Chadwick To: Doug Ambrisko Message-ID: <20100514141514.GA1075@icarus.home.lan> References: <4BECD1CB.9060902@mail.ru> <201005141416.o4EEGS6E057680@ambrisko.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201005141416.o4EEGS6E057680@ambrisko.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: rihad , freebsd-stable@FreeBSD.org Subject: Re: Enabling watchdog X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2010 14:15:17 -0000 On Fri, May 14, 2010 at 07:16:28AM -0700, Doug Ambrisko wrote: > rihad writes: > | On 05/14/2010 04:13 AM, Doug Ambrisko wrote: > | > rihad writes: > | > | Hi, I'm thinking of enabling the watchdog on our Dell PowerEdge 2950 / > | > | FreeBSD 8.0 amd64, so that it reboots the machine in case of lockups. > | > | Right now it doesn't work: > | > | > | > | # watchdog > | > | watchdog: patting the dog: Operation not supported > | > | # > | > | Looking through the kernel configuration I found two relevant settings: > | > | In /sys/conf/NOTES: > | > | # > | > | # Add software watchdog routines. > | > | # > | > | options SW_WATCHDOG > | > | > | > | and in /sys/amd64/conf/NOTES: > | > | # > | > | # Watchdog routines. > | > | # > | > | options MP_WATCHDOG > | > | > | > | Which of them should I rebuild the kernel with? BTW, the existing kernel > | > | is built with the default "options SCHED_ULE" to make good use of > | > | multiple CPUs, does watchdog work with it? > | > > | > If no one has said yet, kldload ipmi then run watchdogd. ... or compile > | > it into the kernel. This will enable the IPMI HW watchdog. If it triggers, > | > it will appear in the IPMI SEL (ipmitool sel list). > | > | Thanks. So did I understand it right that I should first install > | sysutils/ipmitool, then start polling "ipmitool sel list" in a shell > | script from a cron job run once a minute, and reboot in case IPMI > | triggers? But if it's a kernel lockup, none of the user level code might > | run at all. Any way to fall back to a hard and fast kernel level machine > | reset? > > Nope, when you load the ipmi driver it provides a HW watchdog via ipmi > and works with watchdogd. Now if you want to know if your machines > rebooted due to the watchdog then check the ipmi sel for the watchdog > event. I'm a bit confused at this point, Doug. At what point did the OP state he has IPMI support or IPMI cards in his system? -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |