[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.WNT.2.00.1005250926320.2708@jbrandeb-desk1.amr.corp.intel.com>
Date: Tue, 25 May 2010 09:27:25 -0700 (Pacific Daylight Time)
From: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
cc: "stable@...nel.org" <stable@...nel.org>,
"greg@...ah.com" <greg@...ah.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
Brandon <brandon@...p.org>
Subject: Re: [stable-2.6.32 PATCH] ixgbe: backport bug fix for tx panic
On Tue, 25 May 2010, Jeff Kirsher wrote:
> On Mon, May 10, 2010 at 17:46, Jeff Kirsher <jeffrey.t.kirsher@...el.com> wrote:
> > From: Jesse Brandeburg <jesse.brandeburg@...el.com>
> >
> > backporting this commit:
> >
> > commit fdd3d631cddad20ad9d3e1eb7dbf26825a8a121f
> > Author: Krishna Kumar <krkumar2@...ibm.com>
> > Date: Wed Feb 3 13:13:10 2010 +0000
> >
> > ixgbe: Fix return of invalid txq
> >
> > a developer had complained of getting lots of warnings:
> >
> > "eth16 selects TX queue 98, but real number of TX queues is 64"
> >
> > http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg02200.html
> >
> > As there was no follow up on that bug, I am submitting this
> > patch assuming that the other return points will not return
> > invalid txq's, and also that this fixes the bug (not tested).
> >
> > Signed-off-by: Krishna Kumar <krkumar2@...ibm.com>
> > Signed-off-by: Jesse Brandeburg <jesse.brandeburg@...el.com>
> > Acked-by: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>
> > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> > Signed-off-by: David S. Miller <davem@...emloft.net>
> >
> > CC: Brandon <brandon@...p.org>
> > Signed-off-by: Jesse Brandeburg <jesse.brandeburg@...el.com>
> > ---
> >
> > drivers/net/ixgbe/ixgbe_main.c | 8 ++++++--
> > 1 files changed, 6 insertions(+), 2 deletions(-)
> >
>
> Greg - status? Did you queue this patch for the stable release and I missed it?
Maybe we didn't say (and we should have) that this fixes a panic on
machines with > 64 cores. Please apply to -stable 32.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists