Date: Thu, 31 Aug 2006 14:03:19 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "Joe Holden" <joe@joeholden.co.uk> Cc: Rob Watt <rob@hudson-trading.com>, freebsd-net@freebsd.org Subject: Re: Intel em receive hang and possible pr #72970 Message-ID: <2a41acea0608311403x3943e6afma4de6cadb0ef9558@mail.gmail.com> In-Reply-To: <44F74B12.2030108@joeholden.co.uk> References: <Pine.OSX.4.64.0608311124590.8120@cpe-72-229-120-238.nyc.res.rr.com> <2a41acea0608311338x68e64e4bme2fae9e285ada11e@mail.gmail.com> <44F74B12.2030108@joeholden.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/31/06, Joe Holden <joe@joeholden.co.uk> wrote: > Jack Vogel wrote: > > On 8/31/06, Rob Watt <rob@hudson-trading.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0608311403x3943e6afma4de6cadb0ef9558>