From owner-freebsd-stable@FreeBSD.ORG Fri May 14 04:30:06 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 1C3A3106564A for ; Fri, 14 May 2010 04:30:06 +0000 (UTC) (envelope-from rihad@mail.ru) Received: from mx33.mail.ru (mx33.mail.ru [94.100.176.47]) by mx1.freebsd.org (Postfix) with ESMTP id CD50E8FC0A for ; Fri, 14 May 2010 04:30:05 +0000 (UTC) Received: from [217.25.27.27] (port=35370 helo=[217.25.27.27]) by mx33.mail.ru with asmtp id 1OCmXD-0002vl-00; Fri, 14 May 2010 08:30:03 +0400 Message-ID: <4BECD1CB.9060902@mail.ru> Date: Fri, 14 May 2010 09:30:03 +0500 From: rihad User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: Doug Ambrisko References: <201005132313.o4DNDBrp078232@ambrisko.com> In-Reply-To: <201005132313.o4DNDBrp078232@ambrisko.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: Not detected X-Mras: Ok 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 04:30:06 -0000 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?