From: Dipankar Sarma <dipankar@in.ibm.com>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
jens.laas@data.slu.se, hans.liss@its.uu.se,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel panic: Route cache, RCU, possibly FIB trie.
Date: Tue, 21 Mar 2006 03:39:56 +0530 [thread overview]
Message-ID: <20060320220956.GA24792@in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603202234400.27140@ask.diku.dk>
On Mon, Mar 20, 2006 at 10:44:21PM +0100, Jesper Dangaard Brouer wrote:
>
> Kernel panic report.
>
> Have experienced some kernel panic's on a production Linux box acting
> as a router for a large number of customers.
>
> I have tried to track down the problem, and I think I have narrowed it
> a bit down. My theory is that it is related to the route cache
> (ip_dst_cache) or FIB, which cannot dealloacate route cache slab
> elements (maybe RCU related). (I have seen my route cache increase to
> around 520k entries using rtstat, before dying).
>
> I'm using the FIB trie system/algorithm (CONFIG_IP_FIB_TRIE). Think
> that the error might be cause by the "fib_trie" code. See the syslog,
> output below.
>
> Below are some kernel panic outputs from the console and some
> interesting errors found in syslog.
>
> Kernel panic#1
> --------------
> EIP is at _stext+0x3feffd68/0x49
> c03f7380
> Call Trace:
> [<c0103cc7>] show_stack+0x80/0x96
> [<c0103e60>] show_registers+0x161/0x1c5
> [<c0104057>] die+0x107/0x186
> [<c0116c5f>] do_page_fault+0x2c6/0x57d
> [<c0103997>] error_code+0x4f/0x54
> [<c012fe7b>] __rcu_process_callbacks+0xaa/0xd3
> [<c012feff>] rcu_process_callbacks+0x5b/0x65
> [<c0124578>] tasklet_action+0x77/0xc9
> [<c01241f1>] __do_softirq+0xc1/0xd6
> [<c0124251>] do_softirq+0x4b/0x4d
> [<c012433b>] irq_exit+0x47/0x49
> [<c010533b>] do_IRQ+0x2b/0x3b
> [<c010383e>] common_interrupt+0x1a/0x20
> Code: Bad EIP value.
> <0>Kernel panic - not syncing: Fatal exception in interrupt
Bad eip in processing rcu callback often indicates that the object
that embeds the rcu_head has already been freed. Can you enable
slab debugging and see if this can be detected there in a different
path ?
Thanks
Dipankar
next prev parent reply other threads:[~2006-03-20 22:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 21:44 Kernel panic: Route cache, RCU, possibly FIB trie Jesper Dangaard Brouer
2006-03-20 22:09 ` Dipankar Sarma [this message]
2006-03-21 10:29 ` Jesper Dangaard Brouer
2006-03-21 10:37 ` David S. Miller
2006-03-21 14:51 ` Jesper Dangaard Brouer
2006-03-21 21:25 ` David S. Miller
2006-03-23 15:35 ` Jesper Dangaard Brouer
2006-03-23 15:44 ` Jesper Dangaard Brouer
2006-03-23 16:15 ` Eric Dumazet
2006-03-23 21:37 ` Jesper Dangaard Brouer
2006-03-24 6:11 ` Eric Dumazet
2006-03-24 10:34 ` Jesper Dangaard Brouer
2006-03-23 21:32 ` Robert Olsson
2006-03-21 13:28 ` Robert Olsson
2006-03-21 15:27 ` Jesper Dangaard Brouer
2006-03-21 15:37 ` Eric Dumazet
2006-03-21 15:43 ` Dipankar Sarma
2006-03-21 16:30 ` Eric Dumazet
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=20060320220956.GA24792@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=Robert.Olsson@data.slu.se \
--cc=hans.liss@its.uu.se \
--cc=hawk@diku.dk \
--cc=jens.laas@data.slu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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