From owner-freebsd-net@FreeBSD.ORG Fri Sep 1 20:10:35 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DFEC16A4DA for ; Fri, 1 Sep 2006 20:10:35 +0000 (UTC) (envelope-from rob@hudson-trading.com) Received: from ms-smtp-03.rdc-nyc.rr.com (ms-smtp-03.rdc-nyc.rr.com [24.29.109.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04F4C43D49 for ; Fri, 1 Sep 2006 20:10:34 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from cpe-72-229-120-238.nyc.res.rr.com (cpe-72-229-120-238.nyc.res.rr.com [72.229.120.238]) by ms-smtp-03.rdc-nyc.rr.com (8.13.6/8.13.6) with ESMTP id k81KAXwn007732; Fri, 1 Sep 2006 16:10:33 -0400 (EDT) Date: Fri, 1 Sep 2006 16:11:18 -0400 (EDT) From: Rob Watt X-X-Sender: rob@cpe-72-229-120-238.nyc.res.rr.com To: Jack Vogel In-Reply-To: <2a41acea0609011251j6691d6ccs1d14051f1c6ee18b@mail.gmail.com> Message-ID: References: <2a41acea0609011251j6691d6ccs1d14051f1c6ee18b@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Rob Watt , freebsd-net@freebsd.org Subject: Re: Intel em receive hang and possible pr #72970 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 20:10:35 -0000 On Fri, 1 Sep 2006, Jack Vogel wrote: > On 9/1/06, Rob Watt wrote: > > This was my earlier point Rob, that delta of the driver WILL NOT > build against 6.1 RELEASE, it has taskqueue changes in it that > are not in the release, as well as a few other small gotchas. > To get that fix you will need to wait for 6.2 if you want it all rolled > into a determined whole. I just noticed this when I tried to compile with the recent em driver files. Since 6.2 is on the semi-near horizon, and since this bug has only been triggered twice, I might be willing to wait until October to try 6.2. What makes this a more urgent issue is it was triggered on our most critical machines, and the effect of triggering the bug causes much of our business to come to a halt until our backup server takes over. If anyone has tweaked or is willing to tweak the new driver changes to work with 6.1 or 6.0 please let me know. Thanks - Rob Watt