From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 07:19:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FA0716A400 for ; Wed, 5 Apr 2006 07:19:18 +0000 (UTC) (envelope-from rutger.bevaart@illian-networks.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF52C43D45 for ; Wed, 5 Apr 2006 07:19:17 +0000 (GMT) (envelope-from rutger.bevaart@illian-networks.nl) Received: from [192.168.3.5] (237192.xs4all.nl [194.109.237.192]) by smtp-vbr15.xs4all.nl (8.13.6/8.13.6) with ESMTP id k357JBha076441; Wed, 5 Apr 2006 09:19:12 +0200 (CEST) (envelope-from rutger.bevaart@illian-networks.nl) In-Reply-To: <20060404235300.GA7203@mail.der-keiler.de> References: <35547AA9-77E7-47C6-8897-7CC09273118A@illian-networks.nl> <20060404235300.GA7203@mail.der-keiler.de> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1ADDD9D4-57E0-4D2E-B2F0-54B55A699E80@illian-networks.nl> Content-Transfer-Encoding: 7bit From: Rutger Bevaart Date: Wed, 5 Apr 2006 09:18:58 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Ulrich Keil Subject: Re: FreeBSD unstable on Dell 1750 using SMP? 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: Wed, 05 Apr 2006 07:19:18 -0000 It doesn't look like a power problem. We have it with several systems in different datacenters. I've tried the "giantlock" setting, let's hope it works! Am I safe to assume that it can (negatively) impact performance of the system? What can be the cause of "fine grained locking" causing the crashes? I'm willing to let a developer play around with one of the affected machines... Thanks again for the suggestion Ulrich. Met vriendelijke groet / Kind Regards, Rutger Bevaart On Apr 5, 2006, at 1:53 AM, Ulrich Keil wrote: > > We solved the problem by running the network stack with Giant lock > (set "debug.mpsafenet=0" in loader.conf). > Since then the machine runs rock stable. > > Ulrich >