[OLSR-users] kernel oops: NULL pointer deference on a wireless repeater

dennis khoo (spam-protected)
Thu Jun 2 07:05:30 CEST 2005


Hi all,

I seem to run into some problem with 0.4.9, no plugins
were built or used.  The setup is 2 nodes. The first
node is a wireless AP with an ethernet connection to
the internet.  The olsrd.conf is basically
olsrd.conf.default.lq with

Hna4
{
   0.0.0.0      0.0.0.0
}

and the wireless interface block enabled.

The second node has a client radio (associated with
the first node) and another radio running as master
mode(but no one associates with it yet). So the 2nd
node basically functions as a repeater.

The problem is after starting olsrd for some
time(ranging from 10 mins to 3 hours), I will
encounter a null pointer dereference on the 2nd node,
always at the same EIP.  I don't get a core dump since
the kernel panics and restarts but here's what I see:

# Unable to handle kernel NULL pointer dereference at
virtual address 00
000034
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c481fd2c>]    Not tainted
EFLAGS: 00010246
eax: 00000000   ebx: c11dd810   ecx: c11dd956   edx:
c11dd800
esi: c3c87000   edi: c11dd834   ebp: c3aafb6c   esp:
c3aafb54
ds: 0018   es: 0018   ss: 0018
Process olsrd (pid: 23626, stackpage=c3aaf000)
Stack: c3c9a000 c11dde28 00000000 c11dd810 c11dd810
00000000 c3aafbdc c481f0b4
       c3c87000 c11dd810 00000000 00000000 c3c50ae4
c3c70162 c3aafbdc c3aafba4
       00000000 0000092a 00000001 00000000 00000000
c3aafc7c c3c87820 c11dd810
Call Trace:    [<c481f0b4>] [<c48369ec>] [<c48449d4>]
[<c48206f6>] [<c480a127>]
  [<c480b5e3>] [<c480fffe>] [<c0233ab4>] [<c480ac6c>]
[<c0240cce>] [<c023727e>]
  [<c024e2b3>] [<c024e220>] [<c023e840>] [<c024cc77>]
[<c024e220>] [<c024e200>]
  [<c024e20d>] [<c023e840>] [<c024dae5>] [<c024e200>]
[<c0266f83>] [<c0266b00>]
  [<c026d039>] [<c0230795>] [<c0231570>] [<c480b94a>]
[<c480765b>] [<c4807650>]
  [<c0170e9c>] [<c01738d6>] [<c0170dca>] [<c0170d01>]
[<c0231dab>] [<c0160903>]
  [<c016002b>]

Code: 8b 48 34 85 c9 8d 96 9c 01 00 00 75 23 83 ec 0c
6a 00 68 18
 <0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing


Can anyone recommend a quick way to find out where in
the source the problem is coming from. Any help is
deeply appreciated.

dennis


		
__________________________________ 
Discover Yahoo! 
Get on-the-go sports scores, stock quotes, news and more. Check it out! 
http://discover.yahoo.com/mobile.html



More information about the Olsr-users mailing list