From owner-freebsd-net@FreeBSD.ORG Thu Aug 31 21:03:24 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 9934216A4E0 for ; Thu, 31 Aug 2006 21:03:24 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9FEA43D78 for ; Thu, 31 Aug 2006 21:03:20 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so886905pye for ; Thu, 31 Aug 2006 14:03:20 -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=CZofMFRf7fZZW8as0vEQeDzJe+C2t+lDYnZXotFQQoBN5gWLq1nkO+FWzy3FRWZ9mO81BtC/JFXkUl6zw0gf0Iz44E8DbE4N85DRgiXd+muqKJX6JAE7Tduwpaf+7sbnwAi1G9k5wC7va480A5Osyawa1hIIztQWKo8NKiAnFDs= Received: by 10.35.106.1 with SMTP id i1mr1449176pym; Thu, 31 Aug 2006 14:03:20 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Thu, 31 Aug 2006 14:03:19 -0700 (PDT) Message-ID: <2a41acea0608311403x3943e6afma4de6cadb0ef9558@mail.gmail.com> Date: Thu, 31 Aug 2006 14:03:19 -0700 From: "Jack Vogel" To: "Joe Holden" In-Reply-To: <44F74B12.2030108@joeholden.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0608311338x68e64e4bme2fae9e285ada11e@mail.gmail.com> <44F74B12.2030108@joeholden.co.uk> 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: Thu, 31 Aug 2006 21:03:24 -0000 On 8/31/06, Joe Holden wrote: > Jack Vogel wrote: > > 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 > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > IF you want latest -STABLE you use stable, if you want code AS-IS when > it was released, you use RELEASE > I agree with that in the case of generic OS, but from the standpoint of a driver developer/maintainer I hope you see why this is a problem, yes? In the commercial world they dont want to upgrade a complete OS to get a couple line bug fix in a driver, so making the driver backward compatible WHEN POSSIBLE (and I know thats not always doable) is goodness. Jack