From owner-freebsd-current@FreeBSD.ORG Thu Oct 14 17:12:28 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 E01B716A4CE for ; Thu, 14 Oct 2004 17:12:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73A8F43D3F for ; Thu, 14 Oct 2004 17:12:28 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.200] ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i9EHCDKL020576; Thu, 14 Oct 2004 11:12:13 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <416EB324.4040205@freebsd.org> Date: Thu, 14 Oct 2004 11:11:00 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrey Chernov References: <20041014000822.GA30887@nagual.pp.ru> <20041014164044.GA52765@nagual.pp.ru> In-Reply-To: <20041014164044.GA52765@nagual.pp.ru> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Bruce M Simpson cc: Robert Huff cc: current@freebsd.org cc: Ian FREISLICH cc: Robert Watson 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 17:12:29 -0000 Andrey Chernov wrote: > 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, I just searched the PR database and I can't find any reports from you related to this problem. I've also reviewed all of the email on this subject and I can't find any actual details of the problem from you nor any hint that you've attempted to debug it. I'm also not aware of Robert or any other developer being on paid contract by you to guarantee that your hardware works. And since you yourself are a developer and former Core team member, I'm a little curious why you are upset that other volunteers aren't jumping to your needs while you make no effort to help yourself or even file a bug report. Making the network stack run without Giant is a big task, and any problems that exist certainly are not intentional nor due to lack of effort. That said, this is indeed a serious bug and we need to fix it. Scott