From owner-freebsd-current@FreeBSD.ORG Wed Oct 13 23:23:26 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 AAF2616A4CF; Wed, 13 Oct 2004 23:23:26 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B78F43D1F; Wed, 13 Oct 2004 23:23:25 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id A5EC865339; Thu, 14 Oct 2004 00:23:24 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 32275-04-2; Thu, 14 Oct 2004 00:23:24 +0100 (BST) Received: from empiric.dek.spc.org (adsl-67-121-95-134.dsl.snfc21.pacbell.net [67.121.95.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id E62C1651FC; Thu, 14 Oct 2004 00:23:23 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 066C163E8; Wed, 13 Oct 2004 16:23:18 -0700 (PDT) Date: Wed, 13 Oct 2004 16:23:18 -0700 From: Bruce M Simpson To: Robert Watson Message-ID: <20041013232318.GN718@empiric.icir.org> References: <16749.29947.220930.46409@jerusalem.litteratus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: Robert Huff cc: current@freebsd.org 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: Wed, 13 Oct 2004 23:23:26 -0000 On Wed, Oct 13, 2004 at 04:27:22PM -0400, Robert Watson wrote: > There appears to bea problem with if_de cards and Giant-free operation. > I'm working with John Baldwin to try and diagnose it. Could you try > putting debug.mpsafenet=0 in /boot/loader.conf and reboot to confirm that > this is what's going on? The de(4) driver is a bit of a mess as regards locking. I had a look at this back in June/July but no longer have the hardware. It would probably be best to bring it under IFF_NEEDSGIANT. BMS