From owner-freebsd-current@FreeBSD.ORG Thu Oct 14 16:40:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AF9516A4DB; Thu, 14 Oct 2004 16:40:47 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7362243D41; Thu, 14 Oct 2004 16:40:46 +0000 (GMT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id i9EGejEl053817; Thu, 14 Oct 2004 20:40:45 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.13.1/8.13.1/Submit) id i9EGejkO053816; Thu, 14 Oct 2004 20:40:45 +0400 (MSD) (envelope-from ache) Date: Thu, 14 Oct 2004 20:40:44 +0400 From: Andrey Chernov To: Ian FREISLICH Message-ID: <20041014164044.GA52765@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Ian FREISLICH , Kris Kennaway , Bruce M Simpson , Robert Watson , Robert Huff , current@FreeBSD.ORG References: <20041014000822.GA30887@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.28.0.7; VDF 6.28.0.15 (host: pobrecita.freebsd.ru) cc: Bruce M Simpson cc: Robert Huff cc: Robert Watson cc: current@FreeBSD.ORG cc: Kris Kennaway Subject: Re: network slowness/freez-up since update 10/11 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 16:40:47 -0000 On Thu, Oct 14, 2004 at 02:59:34PM +0200, Ian FREISLICH wrote: > but zero response IIRC. Maybe making it on by default was a little > hasty, but anyone that follows -CURRENT like they should if they > run it weuld have been aware of this and set debug.mpsafenet=0 in > their loader.conf when they saw that commit. There is nowhere said in this commit that if_de would or ever may be broken. Everydays something new coming, and this commit is one between similar others, nothing brings special attention to be aware of. I'll expect special 'WARNING: de owners' message to current in such situations, i.e. if something is not fixed to work together. -- Andrey Chernov | http://ache.pp.ru/