From owner-freebsd-net@FreeBSD.ORG Wed May 24 13:53:05 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6330B16A4CB for ; Wed, 24 May 2006 13:53:05 +0000 (UTC) (envelope-from steinex@nognu.de) Received: from shodan.nognu.de (shodan.nognu.de [85.14.216.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id D929143D46 for ; Wed, 24 May 2006 13:53:04 +0000 (GMT) (envelope-from steinex@nognu.de) Received: by shodan.nognu.de (Postfix, from userid 1002) id B177DB857; Wed, 24 May 2006 15:53:02 +0200 (CEST) Date: Wed, 24 May 2006 15:53:02 +0200 From: Frank Steinborn To: Michel Gravey Mail-Followup-To: Michel Gravey , freebsd-net@freebsd.org References: <20060524152346.e4v0qc89w48g4cws@webmail.7ici.biz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060524152346.e4v0qc89w48g4cws@webmail.7ici.biz> User-Agent: mutt-ng/devel-r804 (FreeBSD) Message-Id: <20060524135302.B177DB857@shodan.nognu.de> Cc: freebsd-net@freebsd.org Subject: Re: question about MPSAFE network stack disabled X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 13:53:05 -0000 Michel Gravey wrote: > Hello all, > I've got the following message during boot (on a 6.1 release custom kernel) > WARNING: MPSAFE network stack disabled, expect reduced performance. [...] > Would you please help me to find the cause of that message, to fix the > resulting degraded performance induced by that problem. First: What version are you running? IIRC, MPSAFE was disabled somewhere in the early stages of 5.x - are you running such a version? Second, please check your /boot/loader.conf - could it be that you added that line: debug.mpsafenet="0"? If so, remove it. It's only needed to workaround a bug in FreeBSD-pf AFAIK.