From: David Miller <davem@davemloft.net>
To: jesse.brandeburg@intel.com
Cc: netdev@vger.kernel.org, jeffrey.e.pieper@intel.com
Subject: Re: [net-2.6][2.6.38-rc2] panic during stress testing
Date: Tue, 08 Feb 2011 13:51:13 -0800 (PST) [thread overview]
Message-ID: <20110208.135113.59683468.davem@davemloft.net> (raw)
In-Reply-To: <1297189925.4087.8.camel@jbrandeb-mobl2>
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
Date: Tue, 08 Feb 2011 10:32:05 -0800
> We are currently testing patches and ran into this panic, doesn't
> immediately seem related to the driver.
>
> During TCP/UDP ipv4/6 stress testing on 82574L, 2.6.38-rc2 x86_64
> (net-2.6 with e1000e patches under test) gets numerous OOM killer
> messages, followed by a bug/Oops and panic. could not reproduce the
> bug/panic on 2.6.37, but the OOM killer messages are still seen.
>
> Could well be related somehow to testing with DEBUG_PAGEALLOC enabled.
>
> panic dump and .config follows:
>
> BUG: unable to handle kernel paging request at ffffffff81089738
> IP: [<ffffffff812e2139>] dst_destroy+0x4b/0xf3
> PGD 1695067 PUD 1699063 PMD 10001e1
> Oops: 0003 [#1] PREEMPT SMP DEBUG_PAGEALLOC
> last sysfs file: /sys/devices/system/cpu/cpu3/cache/index2/shared_cpu_map
> CPU 1
> Modules linked in: nfsd exportfs lockd sunrpc dca e1000e [last unloaded: igb]
So some piece of freed memory is being referenced in dst_destroy(), can you
match dst_destroy+0x4b to a line in that function for your build?
You should always do this when submitting a trace like this.
Thanks.
next prev parent reply other threads:[~2011-02-08 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 18:32 [net-2.6][2.6.38-rc2] panic during stress testing Jesse Brandeburg
2011-02-08 21:51 ` David Miller [this message]
2011-02-09 18:12 ` Brandeburg, Jesse
2011-02-09 20:46 ` David Miller
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=20110208.135113.59683468.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.e.pieper@intel.com \
--cc=jesse.brandeburg@intel.com \
--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).