From owner-freebsd-stable@FreeBSD.ORG Sat Sep 30 09:11:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6604B16A403; Sat, 30 Sep 2006 09:11:08 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id EACDC43D4C; Sat, 30 Sep 2006 09:11:07 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1A1E046BF4; Sat, 30 Sep 2006 05:11:07 -0400 (EDT) Date: Sat, 30 Sep 2006 10:11:07 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Scott Long In-Reply-To: <451E1063.60401@samsco.org> Message-ID: <20060930100853.I53010@fledge.watson.org> References: <20060929072741.GH14975@tnn.dglawrence.com> <20060929104427.GN14975@tnn.dglawrence.com> <451E1063.60401@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Pete French , freebsd-stable@freebsd.org, jhb@freebsd.org, ob@e-Gitt.NET Subject: Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 09:11:08 -0000 On Sat, 30 Sep 2006, Scott Long wrote: > David G Lawrence wrote: > >>>> Attached is a simple user program that will immediately cause pretty >>>> much >>>> all of the network drivers (at least the ones I own) to stop working and >>>> get watchdog timeouts. >>> >>> I am runnign this on a single processor machine with an SMP kernel and >>> it does not have any effect. I dont tink I have any single processor >>> machines >>> running a non SMP kernel to try it on though. Not particularly helpful I >>> know. I'll >> >> Actually, I think it is helpful to know that the program only has an >> effect on some machines. We just need to figure out what the common >> denominator is. > > Are you enabling an option, like IPv6, that puts Giant over the network > stack? IPv6 has Giant over its netisr, but not over the entire network stack. If Giant is being placed over the stack due to use of an option that forces it (such as KAME IPSEC) you should be able to grep this out of dmesg by doing something along the lines of the following: grep "WARNING: debug.mpsafenet" /var/run/dmesg Robert N M Watson Computer Laboratory University of Cambridge