From owner-freebsd-current@FreeBSD.ORG Mon Nov 1 19:55:42 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 8651916A4CE; Mon, 1 Nov 2004 19:55:42 +0000 (GMT) Received: from a80-126-165-168.adsl.xs4all.nl (a80-126-165-168.adsl.xs4all.nl [80.126.165.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36B9B43D2D; Mon, 1 Nov 2004 19:55:42 +0000 (GMT) (envelope-from devet@devet.org) Received: from adv.devet.org (adv.devet.org [192.168.1.2]) by a80-126-165-168.adsl.xs4all.nl (Postfix) with ESMTP id 56316D6EC; Mon, 1 Nov 2004 20:55:41 +0100 (CET) Received: by adv.devet.org (Postfix, from userid 100) id 503DC2636A; Mon, 1 Nov 2004 20:55:41 +0100 (CET) Date: Mon, 1 Nov 2004 20:55:41 +0100 From: Arjan de Vet To: Robert Watson Message-ID: <20041101195541.GA1461@adv.devet.org> References: <20041101164723.GA7375@adv.devet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: if_sk patch to get more info from people with problems 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: Mon, 01 Nov 2004 19:55:42 -0000 Robert Watson wrote: >> I filed a bug report for if_sk.c for possibly related symptoms: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F73038 The >> IFF_NEEDSGIANT flag seems to solve the problem but I need to do much >> more testing with it this week (had to go back to 5.2.1 because 5.3 >> hangs for me after 1-1.5 days; still need to debug that one as well :(). > >Note that it could well be a locking bug in if_sk, but that >debug.mpsafenet and IFF_NEEDSGIANT both substantially change the timing in >the driver, so these changes could just mask an existing bug in your >configuration (yet still leave it present in other's). The if_de bug >recently, btw, turned out to be an existing (real) bug that was unmasked >due to timing changes from running with IFF_NEEDSGIANT, but was in fact >(we believe) present even with Giant over the stack... I just updated kern/73038 to say that the problem I was seeing seems to have disappeared with 5.3-RC2. I am now running 5.3-RC2 with an unmodified if_sk.c and without debug.mpsafenet=0 and so far all network connections behave as usual. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL : http://www.devet.org/ Work: http://www.madison-gurkha.com/ (Security, Open Source, Education)