Recently tested, it crashes also -git6 without lockdep compiled. So it seems

actually networking code bug.
--

Denys Fedoryshchenko

Technical Manager

Virtual ISP S.A.L.
--

From: "Denys Fedoryshchenko" <denys@visp.net.lb>
I'm still not so sure.
The IP is at ip_route_input but the rest of your backtrace

shows an entirely different code path.
Nothing in the trace matches up, which severely decreases the

usability of the debugging information you've provided.
--

What can i do to increase usability?
--

Denys Fedoryshchenko

Technical Manager

Virtual ISP S.A.L.
--

On Sun, 23 Mar 2008 19:17:55 +0200
Enabling CONFIG_FRAME_POINTER tends to make backtraces more reliable.

Making sure that (on 32 bit x86) you use CONFIG_4KSTACKS is enabled also tends

to improve backtrace reliability (less noise from interrupts)
Another good option is to go to www.kerneloops.org and try to see if others

saw similar backtraces but with less noise
--

If you want to reach me at my work email, use arjan@linux.intel.com

For development, discussion and tips for power savings,

visit http://www.lesswatts.org

--

They are both enabled.

There is nothing similar in kerneloops.
CONFIG_DEBUG_RODATA, 4K stacks, Frame pointers, CONFIG_DEBUG_STACKOVERFLOW -

enabled.
It reboots recently after bringing up networking. Sometimes even not reaching

place where i am loading netconsole.
Always in ip_route_input. This is 2.6.25-rc6-git6, 2 panic's. They are easy

to reproduce, but i cannot do bisect, cause this machine dont have power

switch and in difficult to reach area.
Mar 23 21:53:08 ROUTER [    6.986563] BUG: unable to handle kernel

Mar 23 21:53:08 ROUTER paging request

Mar 23 21:53:08 ROUTER at c0106010

Mar 23 21:53:08 ROUTER [    6.986660] IP:

Mar 23 21:53:08 ROUTER [<c027706a>] ip_route_input+0x872/0xbd9

Mar 23 21:53:08 ROUTER [    6.986726] Oops: 0003 [#1]

Mar 23 21:53:08 ROUTER SMP

Mar 23 21:53:08 ROUTER

Mar 23 21:53:08 ROUTER [    6.986814] Modules linked in:

Mar 23 21:53:08 ROUTER nf_conntrack_proto_gre

Mar 23 21:53:08 ROUTER nf_nat_proto_gre

Mar 23 21:53:08 ROUTER netconsole

Mar 23 21:53:08 ROUTER configfs

Mar 23 21:53:08 ROUTER hangcheck_timer

Mar 23 21:53:08 ROUTER xt_tcpudp

Mar 23 21:53:08 ROUTER ipt_TTL

Mar 23 21:53:08 ROUTER ipt_ttl

Mar 23 21:53:08 ROUTER xt_NOTRACK

Mar 23 21:53:08 ROUTER iptable_raw

Mar 23 21:53:08 ROUTER iptable_mangle

Mar 23 21:53:08 ROUTER ifb

Mar 23 21:53:08 ROUTER e1000e

Mar 23 21:53:08 ROUTER em_nbyte

Mar 23 21:53:08 ROUTER cls_tcindex

Mar 23 21:53:08 ROUTER act_gact

Mar 23 21:53:08 ROUTER cls_rsvp

Mar 23 21:53:08 ROUTER sch_htb

Mar 23 21:53:08 ROUTER cls_fw

Mar 23 21:53:08 ROUTER act_mirred

Mar 23 21:53:08 ROUTER em_u32

Mar 23 21:53:08 ROUTER sch_red

Mar 23 21:53:08 ROUTER sch_sfq

Mar 23 21:53:08 ROUTER sch_tbf

Mar 23 21:53:08 ROUTER sch_teql

Mar 23 21:53:08 ROUTER cls_basic

Mar 23 21:53:08 ROUTER act_police

Mar 23 21:53:08 ROUTER sch_gred

Mar 23 21:53:08 ROUTER act_pedit

Mar 23 21:53:08 ROUTER sch_hfsc

Mar 23 21:53:08 ROUTER cls_rsvp6

Mar 23 21:53:08 ROUTER sch_ingress

Mar 23 21:53:08 ROUTER em_meta

Mar 23 21:53:08 ROUTER em_t...
[ message continues ]