From owner-freebsd-stable@FreeBSD.ORG Fri May 14 11:53:27 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 6079F106567F for ; Fri, 14 May 2010 11:53:27 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 332368FC27 for ; Fri, 14 May 2010 11:53:27 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id D812146B92; Fri, 14 May 2010 07:53:26 -0400 (EDT) Received: from John-Baldwins-Macbook-Pro.local (localhost [IPv6:::1]) by bigwig.baldwin.cx (Postfix) with ESMTPA id AE3328A026; Fri, 14 May 2010 07:53:25 -0400 (EDT) Message-ID: <4BED3974.1000704@FreeBSD.org> Date: Fri, 14 May 2010 07:52:20 -0400 From: John Baldwin User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: rihad References: <201005132313.o4DNDBrp078232@ambrisko.com> <4BECD1CB.9060902@mail.ru> In-Reply-To: <4BECD1CB.9060902@mail.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 14 May 2010 07:53:25 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: 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 11:53:27 -0000 rihad wrote: > 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? No, watchdogd and the IPMI driver will manage the watchdog. You can use 'sel elist' after a reboot to see if the reboot was triggered via the watchdog. -- John Baldwin