From: Todd Merritt <tmerritt@email.arizona.edu>
To: netdev@vger.kernel.org
Subject: Re: ixgbe: panic in ixgbe_clean_rx_irq()
Date: Mon, 27 Jul 2009 21:50:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20090727T214746-75@post.gmane.org> (raw)
In-Reply-To: Pine.WNT.4.64.0907241142370.2084@ppwaskie-MOBL2.amr.corp.intel.com
Waskiewicz Jr, Peter P <peter.p.waskiewicz.jr <at> intel.com> writes:
>
> On Fri, 24 Jul 2009, Jesper Dangaard Brouer wrote:
>
> > On Thu, 2009-07-23 at 17:21 +0200, Jesper Dangaard Brouer wrote:
> > > I'm going to run a test with a no-preempt kernel over night...
> >
> > The no-preempt kernel has been stable for 17 hours, while running a four
> > times 10GbE pktgen load test (using 1024 bytes packets).
> >
> > Kernel git version (git describe):
> > v2.6.31-rc1-932-g8e321c4
> >
> > Git ("git log e594e96..8e321c4 drivers/net/ixgbe") reports not changes
> > to the ixgbe driver between these two kernel versions.
>
> Thanks for the additional info Jesper. This is definately a good data
> point. I'm not sure where to go with the preemption debugging at this
> point with our driver under heavy load. We're still trying to repro here.
> I'll keep digging around though in the meantime.
>
> This is the second preemption-induced bug from ixgbe we've had reported in
> a few days. Eek!
>
We're getting a panic in the same function with the stable version of the ixgbe
driver 2.0.38.2-1 on redhat 5 kernel-2.6.18-128.1.10.el5. Is there a dev
release of the driver that might have a fix in it ?
Thanks,
Todd
next prev parent reply other threads:[~2009-07-27 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 12:44 ixgbe: panic in ixgbe_clean_rx_irq() Jesper Dangaard Brouer
2009-07-22 18:13 ` Waskiewicz Jr, Peter P
2009-07-23 8:46 ` Jesper Dangaard Brouer
2009-07-23 15:21 ` Jesper Dangaard Brouer
2009-07-24 8:41 ` Jesper Dangaard Brouer
2009-07-24 18:47 ` Waskiewicz Jr, Peter P
2009-07-27 21:50 ` Todd Merritt [this message]
2009-07-27 22:31 ` Waskiewicz Jr, Peter P
2009-07-28 13:37 ` Todd Merritt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20090727T214746-75@post.gmane.org \
--to=tmerritt@email.arizona.edu \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).