[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080819142410.GA7100@ajones-laptop.nbttech.com>
Date: Tue, 19 Aug 2008 07:24:10 -0700
From: Arthur Jones <ajones@...erbed.com>
To: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
CC: "jeff@...zik.org" <jeff@...zik.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
Bruce Allan <bruce.w.allan@...el.com>
Subject: Re: [UPDATED] [NET-NEXT PATCH 3/3] e1000e: add support for new
82574L part
Hi Jeff, ...
On Mon, Aug 18, 2008 at 12:53:06PM -0700, Jeff Kirsher wrote:
> [...]
> > This is perhaps a dup of the e1000.sf.net bug
> > 2040298 against the linux 2.6.26 + 0.4.1.7 intel
> > e1000e driver:
> >
> > http://sourceforge.net/tracker/index.php?func=detail&aid=2040298&group_id=42302&atid=447449
> >
> > The system info is the same as in that bug, only
> > the kernel and driver have changed...
>
> This is to be expected since these patches get the in kernel driver
> updated or at least close to the out of kernel 0.4.1.7 driver. We are
> aware of the issue and we are currently working the issue.
Very fast work indeed, yesterday I was given new
firmware and today it looks like the issue is resolved.
> Jesse is expecting to get you a patch today to test which should
> resolve the issue.
Yesterday I received from Intel an upgrade from pre-production
(v0.5) 82574 firmware to production (v1.0) firmware and tools to
install it. With the upgrade the problem no longer appears to be
reproducible.
Thanks to all at Intel for tracking this issue down and solving
it. Esp Jesse Brandeburg who kept the e1000.sf.net bug updated
with new things to try and even offered to send along hardware to
help in debugging. Thanks all!
Arthur
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists