Date: Fri, 1 Sep 2006 16:11:18 -0400 (EDT) From: Rob Watt <rob@hudson-trading.com> To: Jack Vogel <jfvogel@gmail.com> Cc: Rob Watt <rob@hudson-trading.com>, freebsd-net@freebsd.org Subject: Re: Intel em receive hang and possible pr #72970 Message-ID: <Pine.OSX.4.64.0609011558350.14344@cpe-72-229-120-238.nyc.res.rr.com> In-Reply-To: <2a41acea0609011251j6691d6ccs1d14051f1c6ee18b@mail.gmail.com> References: <Pine.OSX.4.64.0609011343070.14344@cpe-72-229-120-238.nyc.res.rr.com> <2a41acea0609011251j6691d6ccs1d14051f1c6ee18b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 1 Sep 2006, Jack Vogel wrote: > On 9/1/06, Rob Watt <rob@hudson-trading.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSX.4.64.0609011558350.14344>