From owner-freebsd-questions@FreeBSD.ORG Tue Sep 4 22:03:26 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 8227116A420 for ; Tue, 4 Sep 2007 22:03:26 +0000 (UTC) (envelope-from d.hill@yournetplus.com) Received: from duane.dbq.yournetplus.com (duane.dbq.yournetplus.com [65.124.230.214]) by mx1.freebsd.org (Postfix) with ESMTP id 63F7C13C46A for ; Tue, 4 Sep 2007 22:03:26 +0000 (UTC) (envelope-from d.hill@yournetplus.com) Received: from [192.168.1.10] (unknown [192.168.1.1]) by duane.dbq.yournetplus.com (Postfix) with ESMTP id A1AD16D42E for ; Tue, 4 Sep 2007 22:03:25 +0000 (UTC) Date: Tue, 4 Sep 2007 22:03:25 +0000 (UTC) From: Duane Hill X-X-Sender: d.hill@duane.dbq.yournetplus.com To: freebsd-questions@freebsd.org Message-ID: <20070904214705.S2251@duane.dbq.yournetplus.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 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: Tue, 04 Sep 2007 22:03:26 -0000 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? ------ _|_ (_| |