From owner-freebsd-stable@FreeBSD.ORG Thu Oct 19 21:31: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 6F00416A4B3 for ; Thu, 19 Oct 2006 21:31:32 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.192.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4437B43D69 for ; Thu, 19 Oct 2006 21:31:19 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (rwcrmhc11) with ESMTP id <20061019213119m1100rumqee>; Thu, 19 Oct 2006 21:31:19 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 4200C1FA037; Thu, 19 Oct 2006 14:31:19 -0700 (PDT) Date: Thu, 19 Oct 2006 14:31:19 -0700 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20061019213119.GA74542@icarus.home.lan> Mail-Followup-To: freebsd-stable@freebsd.org References: <2a41acea0610181046k822afd1qcec4187dc8514187@mail.gmail.com> <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> <20061018171704.A3851@demos.bsdclusters.com> <4537C126.5000207@FreeBSD.org> <2a41acea0610191140j13d43e12q72fc7697652e222a@mail.gmail.com> <20061019190221.GH71000@droso.net> <2a41acea0610191418q6c6fac45xdd9ad824bd6cae2f@mail.gmail.com> <20061019212028.GA36814@xor.obsecurity.org> <2a41acea0610191423q537834cfo2d0f2741fa8e8d63@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a41acea0610191423q537834cfo2d0f2741fa8e8d63@mail.gmail.com> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: em network issues 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: Thu, 19 Oct 2006 21:31:32 -0000 On Thu, Oct 19, 2006 at 02:23:54PM -0700, Jack Vogel wrote: > Other suggestions? Is the hardware the same? ACPI being used? APIC being used? How about doing something that shares interrupts simultaneously, like copying mass amounts of data to/from a USB hard disk via USB 2.0 (hence using usb) while copying data over NFS (hence using em)? I could only get the problem to happen when there was both intense network usage **and** intense disk I/O (ata and em shared an interrupt in my case). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |