From owner-freebsd-questions@FreeBSD.ORG Wed Sep 5 00:43:07 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7E3816A419 for ; Wed, 5 Sep 2007 00:43:07 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 29B5813C461; Wed, 5 Sep 2007 00:43:06 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46DDFB98.1010404@FreeBSD.org> Date: Wed, 05 Sep 2007 02:43:04 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Duane Hill References: <20070904214705.S2251@duane.dbq.yournetplus.com> In-Reply-To: <20070904214705.S2251@duane.dbq.yournetplus.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: fatal double fault (spinlock) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Sep 2007 00:43:07 -0000 Duane Hill wrote: > > We have a Dell PowerEdge 6850 with four 3ghz Intel dual core Xeon > processors and 12 gig ram. It is running FreeBSD 5.5-RELEASE-p15 amd64. > SMP has been compiled into the kernel. However, > machdep.hyperthreading_allowed has been set to zero(0) in > /etc/sysctrl.conf. > > Once about every 1.5 to 2 weeks, the server throws the error: > > fatal double fault > cpuid=15 > spinlock sched lock held by 0xffffff032f3c1500 > 5 seconds > > This server is located in a colo many miles away. I had to have a person > at the colo facility read off the message that was on the screen. I hope > it is exact (or at least close). > > This server is one of our main spam filter servers. It use to have an > MTA installed on it that required FreeBSD 5.5. That software does not > run on the server anymore. > > I've been meaning to upgrade the server to 6.2 release, but have been > procrastinating. Would upgrading the server to 6.2 release correct this > issue? Chances are good: by running 5.5 you are missing out on several years of bug fixes. Kris