From: Eric Dumazet <eric.dumazet@gmail.com>
To: "\"Oleg A. Arkhangelsky\"" <sysoleg@yandex.ru>
Cc: netdev@vger.kernel.org
Subject: Re: Kernel panic in fib_rules_lookup (kernel 2.6.32)
Date: Tue, 09 Mar 2010 18:09:28 +0100 [thread overview]
Message-ID: <1268154568.3113.19.camel@edumazet-laptop> (raw)
In-Reply-To: <119601268120674@webmail87.yandex.ru>
Le mardi 09 mars 2010 à 10:44 +0300, "Oleg A. Arkhangelsky" a écrit :
> Hello,
>
> Got this kernel panic tomorrow. This PC is rather heavy loaded router with BGP full view (> 300K routes).
> We're using FIB_TRIE. Last time we got similar panic about 1 month ago. Please, let me know if you
> need additional information to debug (e.g. objdump). Thanks!
>
> Mar 9 10:08:55 bras-1 kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
> Mar 9 10:08:55 bras-1 kernel: IP: [<c11fa012>] fib_rules_lookup+0xa2/0xd0
> Mar 9 10:08:55 bras-1 kernel: *pde = 00000000
> Mar 9 10:08:55 bras-1 kernel: Thread overran stack, or stack corrupted
Hmm...
> Mar 9 10:08:55 bras-1 kernel: Oops: 0000 [#1] SMP
> Mar 9 10:08:55 bras-1 kernel: Modules linked in: ipt_NETFLOW iTCO_wdt xt_tcpudp iptable_filter iptable_nat ip_tables ipt_ISG x_tables ipmi_watchdog ipmi_msghandler nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack 8021q e1000 e1000e
> Mar 9 10:08:55 bras-1 kernel:
> Mar 9 10:08:55 bras-1 kernel: Pid: 0, comm: swapper Not tainted (2.6.32 #3)
Is it an unpatched kernel ?
Could you send us your .config ?
gcc -v ?
next prev parent reply other threads:[~2010-03-09 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 7:44 Kernel panic in fib_rules_lookup (kernel 2.6.32) "Oleg A. Arkhangelsky"
2010-03-09 17:09 ` Eric Dumazet [this message]
2010-05-02 10:46 ` "Oleg A. Arkhangelsky"
2010-05-02 16:31 ` Eric Dumazet
2010-05-02 17:14 ` "Oleg A. Arkhangelsky"
-- strict thread matches above, loose matches on Subject: below --
2010-03-09 17:21 "Oleg A. Arkhangelsky"
2010-03-09 18:22 ` Stephen Hemminger
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=1268154568.3113.19.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sysoleg@yandex.ru \
/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