From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 10:05:37 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 8457C16A41A for ; Mon, 24 Sep 2007 10:05:37 +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 6F91513C448; Mon, 24 Sep 2007 10:05:35 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F78BEF.4070406@FreeBSD.org> Date: Mon, 24 Sep 2007 12:05:35 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Borja Marcos References: <46F78459.4060607@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Benjie Chen 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 10:05:37 -0000 Borja Marcos wrote: > > On 24 Sep 2007, at 11:33, Kris Kennaway wrote: > >> Borja Marcos wrote: >>> 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. >> >> What number is the PR with the details? > > Sorry, I couldn't diagnose anything properly. When it happened the > sysadmin didn't give me the panic details, and being production machines > the main priority was to put them back into service as soon as possible. > > Would it be a good idea to file a PR with such fuzzy information? I > don't think so, that's why I didn't do it. Of course I can do it if > someone thinks it's worth. But unfortunately I cannot get more precise > details. No it isn't. You will need to do some more work to obtain this information, otherwise your bug will probably not be fixed. debug.mpsafenet=0 is no longer an option in 7.0, so you will have to deal with this sooner or later. Kris