From owner-freebsd-stable@FreeBSD.ORG Sat Sep 30 01:03:32 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 0D64916A40F; Sat, 30 Sep 2006 01:03:32 +0000 (UTC) (envelope-from craig@feniz.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCE8743D45; Sat, 30 Sep 2006 01:03:29 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id 5AD41111B2; Fri, 29 Sep 2006 20:03:29 -0500 (CDT) Date: Fri, 29 Sep 2006 20:03:29 -0500 From: Craig Boston To: Kris Kennaway Message-ID: <20060930010328.GC63032@nowhere> References: <451A1375.5080202@gneto.com> <20060927071538.GF22229@e-Gitt.NET> <451A4189.5020906@samsco.org> <20060927152824.GJ22229@e-Gitt.NET> <20060927155553.GB14563@icarus.home.lan> <20060927155904.GM22229@e-Gitt.NET> <451AA7B1.5080202@samsco.org> <20060929072741.GH14975@tnn.dglawrence.com> <20060929212155.GB56501@nowhere> <20060929213740.GA37735@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060929213740.GA37735@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, John Baldwin , Oliver Brandmueller 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 01:03:32 -0000 On Fri, Sep 29, 2006 at 05:37:40PM -0400, Kris Kennaway wrote: > and provide access to that file. > > This will help to show whether something is causing Giant starvation. http://www.gank.org/freebsd/stats.out That's after about 25 seconds of the em0 interface being unable to receive because of an apparent lack of interrupt processing (it can still transmit though! I had a half-open ssh session that continued to receive data for a while). Interesting data point #1: After a fresh boot, I'm unable to reproduce the problem until I use the kernel linker. After kldloading a module (any module) and then immediately unloading it, my test case works 100% until I reboot again. Interesting data point #2: After a reboot, the problem moved from em0 on irq19 to em1 on irq18. I'm remote from the machine right now so I can't test the usb controller that's sharing that interrupt, though I suspect it experienced the same lack of response. Craig