Re: Linux Kernel | Intel Driver Bug - please update

[Jeff Kirsher <jeffrey.t.kirsher@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 4031 bytes --]

On Sat, 2011-08-20 at 14:57 -0700, Nicolás Sigal | LocalHost Soluciones
Innovadoras wrote:
> Jeff, we always use the latest stable release, in this case, v3.0.3

The fixes (and driver bump) went into Linus's 3.1 tree, only one fix was
applied to the "stable" releases.

I would try Linus's 3.1 tree to verify that the issue you have been
seeing is fixed.

> 
> ----- Original Message ----- 
> From: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
> To: "Nicolás Sigal | LocalHost Soluciones Innovadoras" 
> <nicolas.sigal@localhost.net.ar>
> Cc: <kristoffer@gaisler.com>; "Brandeburg, Jesse" 
> <jesse.brandeburg@intel.com>; "Allan, Bruce W" <bruce.w.allan@intel.com>; 
> "Ronciak, John" <john.ronciak@intel.com>; "netdev" <netdev@vger.kernel.org>
> Sent: Saturday, August 20, 2011 6:51 PM
> Subject: Re: Linux Kernel | Intel Driver Bug - please update
> 
> On Sat, 2011-08-20 at 13:35 -0700, Nicolás Sigal | LocalHost Soluciones
> Innovadoras wrote:
> > Please Jeff, we need the update as soon as possible, we still having 
> > crashes
> > of eth because the driver..
> >
> > Best regards;
> >
> 
> The patches have been pushed and accepted.  Are you using Linus's latest
> 3.1 tree?
> 
> >
> > ----- Original Message ----- 
> > From: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
> > To: "Nicolás Sigal | LocalHost Soluciones Innovadoras"
> > <nicolas.sigal@localhost.net.ar>
> > Cc: <kristoffer@gaisler.com>; "Brandeburg, Jesse"
> > <jesse.brandeburg@intel.com>; "Allan, Bruce W" <bruce.w.allan@intel.com>;
> > "Ronciak, John" <john.ronciak@intel.com>; <support@localhost.net.ar>;
> > "netdev" <netdev@vger.kernel.org>
> > Sent: Sunday, July 24, 2011 7:47 PM
> > Subject: Re: Linux Kernel | Intel Driver Bug - please update
> >
> > On Sun, 2011-07-24 at 13:28 -0700, Nicolás Sigal | LocalHost Soluciones
> > Innovadoras wrote:
> > > Please, can you update the e1000e driver of the kernel to v1.4.4?
> > >
> > > http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3299&DwnldID=15817&ProductFamily=Componentes+Ethernet&ProductLine=Controladores+Ethernet&ProductProduct=Controlador+Intel%C2%AE+82579+Gigabit+Ethernet&DownloadType=Controladoresspa
> > >
> > > This version have an important bug fixed:
> > > * 82579: Fix for Tx Hang on FTS ME Platform
> > >
> > > And we have this problem in all of our servers with this NIC and ME
> > > on.
> > >
> > > Debug:
> > >
> > > Jul 24 14:23:27 [kernel] e1000e 0000:00:19.0: eth0: Detected Hardware
> > > Unit Hang:
> > > Jul 24 14:23:27 [kernel]   TDH                  <0>
> > > Jul 24 14:23:27 [kernel]   TDT                  <16>
> > > Jul 24 14:23:27 [kernel]   next_to_use          <16>
> > > Jul 24 14:23:27 [kernel]   next_to_clean        <0>
> > > Jul 24 14:23:27 [kernel] buffer_info[next_to_clean]:
> > > Jul 24 14:23:27 [kernel]   time_stamp           <10282156f>
> > > Jul 24 14:23:27 [kernel]   next_to_watch        <0>
> > > Jul 24 14:23:27 [kernel]   jiffies              <102821aed>
> > > Jul 24 14:23:27 [kernel]   next_to_watch.status <0>
> > > Jul 24 14:23:27 [kernel] MAC Status             <80143>
> > > Jul 24 14:23:27 [kernel] PHY Status             <796d>
> > > Jul 24 14:23:27 [kernel] PHY 1000BASE-T Status  <0>
> > > Jul 24 14:23:27 [kernel] PHY Extended Status    <3000>
> > > Jul 24 14:23:27 [kernel] PCI Status             <10>
> > > Jul 24 14:23:28 [kernel] e1000e 0000:00:19.0: eth0: Reset adapter
> > > Jul 24 14:23:30 [kernel] e1000e: eth0 NIC Link is Up 100 Mbps Full
> > > Duplex, Flow Control: Rx/Tx
> > > Jul 24 14:23:30 [kernel] e1000e 0000:00:19.0: eth0: 10/100 speed:
> > > disabling TSO
> > >
> >
> >
> > [removed ixgbe/igb Intel maintainers, and Linus from the email thread]
> > Added a more appropriate mailing list (netdev)
> >
> > We currently have the kernel patches in review and testing to update the
> > e1000e driver to v1.4.4.  I should be able to push some, if not all of
> > the changes upstream later this week.
> >
> 
> 
> 



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]