From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 08:49:00 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57A5F16A420 for ; Mon, 24 Sep 2007 08:49:00 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from proxypop1.sarenet.es (proxypop1.sarenet.es [194.30.0.99]) by mx1.freebsd.org (Postfix) with ESMTP id 0721913C465 for ; Mon, 24 Sep 2007 08:49:00 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from [127.0.0.1] (matahari.sarenet.es [192.148.167.18]) by proxypop1.sarenet.es (Postfix) with ESMTP id 73EF55CC5; Mon, 24 Sep 2007 10:48:58 +0200 (CEST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Borja Marcos Date: Mon, 24 Sep 2007 10:48:57 +0200 To: "Benjie Chen" X-Mailer: Apple Mail (2.752.2) Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 08:49:00 -0000 On 22 Sep 2007, at 00:26, Benjie Chen wrote: > FreeBSD 6.2 on PowerEdge 1950, RAID1 setup with mfi driver > (PERC5i). 4GB > RAM. I am currently running i386, and not amd64, due to various > reasons. > > Kernel panic is at 0xC066C731, which from nm shows it's in > mtx_lock_spin > c066c7b4 T _mtx_lock_spin > c066c85c T _mtx_unlock_sleep > > So this could mean that independent stress tests will not result in > panic if > there aren't enough concurrency to cause the problem. I don't have the exact IP address involved, but we experienced consistent panics in two heavily loaded mail servers (same hardware models, Dell Powereedge) runnning Postfix and FreeBSD 6.2. Suspecting an issue with the IP stack and smp I tried to set "debug.mpsafenet=0" and the problems are gone. Of course I've lost some performance, but the systems have been solid for some weeks so far. Borja. ---------------- "The thing he realised about the windows was this: because they had been converted into openable windows after they had first been designed to be impregnable, they were, in fact, much less secure than if they had been designed as openable windows in the first place." Douglas Adams, "Mostly Harmless"