From owner-freebsd-net@FreeBSD.ORG Thu Aug 31 20:40:21 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 4370316A4DE for ; Thu, 31 Aug 2006 20:40:21 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA2E443D46 for ; Thu, 31 Aug 2006 20:40:20 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so880681pye for ; Thu, 31 Aug 2006 13:40:11 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IjDAy4punjiBaV+kcr2yTiYWl4uxrAjCC6oqcAAU5Whn6oaqEtvVGFhdPjUhm/D4lwGn5mEqKwRJ93oPHuTRJbKzDYEQkhHS9I6WPrbl8pTCuxt4ENGmDoPFdboTASTQiiREEUdakxZhK8Giw7AiXRLAOGxF823Chy98H2sqOkY= Received: by 10.35.105.18 with SMTP id h18mr1395871pym; Thu, 31 Aug 2006 13:38:40 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Thu, 31 Aug 2006 13:38:40 -0700 (PDT) Message-ID: <2a41acea0608311338x68e64e4bme2fae9e285ada11e@mail.gmail.com> Date: Thu, 31 Aug 2006 13:38:40 -0700 From: "Jack Vogel" To: "Rob Watt" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: 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: Thu, 31 Aug 2006 20:40:21 -0000 On 8/31/06, Rob Watt wrote: > After poking around in various group/pr postings the most similar problem > that we found was PR #72970. > http://www.freebsd.org/cgi/query-pr.cgi?pr=72970 > > Does it seem that we are encountering that bug? Is that bug fixed in > 6.1-RELEASE, or is there an easy patch to 6.0-RELEASE (i.e. can we only > patch the em driver). That fix is only just into the STABLE code, so no, not in 6.1-RELEASE. You could take the tip of STABLE, but if you have only a 6.0 based system I know you are going to run into some backward incompatabililties. As a matter of fact I dont believe the STABLE tip will even build on RELEASE (something that I take issue with). Sounds like its at least possible this is your problem, worth setting up a system to test with I would say. Good Luck, Jack Intel LAD