[Openswan dev] Possible issue between Openswan 2.1 branch and Madwifi?

Nate Carlson natecars at natecarlson.com
Mon May 17 10:36:35 CEST 2004


Just wondering, does anyone else use Openswan on a box with the Madwifi
driver (it's a driver for the Atheros wifi cards).

I tried to set it up on one of my boxes (Openswan 2.1 branch from
05/13/2004), and consistently get the following dump from snmpd right
after I start Openswan:

May 14 17:40:02 carbon kernel: Unable to handle kernel NULL pointer dereference at virtual address 000000ec
May 14 17:40:02 carbon kernel:  printing eip:
May 14 17:40:02 carbon kernel: c4867a76
May 14 17:40:02 carbon kernel: *pde = 00000000
May 14 17:40:02 carbon kernel: Oops: 0002
May 14 17:40:02 carbon kernel: CPU:    0
May 14 17:40:02 carbon kernel: EIP:    0010:[<c4867a76>]    Tainted: P
May 14 17:40:02 carbon kernel: EFLAGS: 00010246
May 14 17:40:02 carbon kernel: eax: 00000000   ebx: c19b7f68   ecx: 00000000   edx: c19b7f04
May 14 17:40:02 carbon kernel: esi: 00000000   edi: c19b7f14   ebp: c3705400   esp: c19b7ef4
May 14 17:40:02 carbon kernel: ds: 0018   es: 0018   ss: 0018
May 14 17:40:02 carbon kernel: Process snmpd (pid: 464, stackpage=c19b7000)
May 14 17:40:02 carbon kernel: Stack: c19b7f04 00000000 c19b7f54 c10e4e60 ec495788 00000000 00000000 00000000
May 14 17:40:02 carbon kernel:        000089f0 c3705400 c19b7f54 c19b7f54 c020c55f c3705400 c19b7f54 000089f0
May 14 17:40:02 carbon kernel:        c19b7f54 00000000 00000001 000089f0 c020c781 c19b7f54 000089f0 00000020
May 14 17:40:02 carbon kernel: Call Trace:    [dev_ifsioc+975/1088] [dev_ioctl+433/800] [sock_ioctl+38/48] [sys_ioctl+201/592] [sys_fstat64+73/128]
May 14 17:40:02 carbon kernel:   [system_call+51/56]
May 14 17:40:02 carbon kernel:
May 14 17:40:02 carbon kernel: Code: ff 0d ec 00 00 00 0f 94 c0 84 c0 75 0a b8 fa ff ff ff e9 fd

If I drop back to Freeswan 2.04, things work without any problems. (This
is why I'm suspecting an Openswan problem instead of a Madwifi problem).  
No clue why it causes snmpd to dump out.  :) After this happens, any calls
to 'ifconfig', 'route', etc. just hang when running them.

If anyone has any ideas on how to troubleshoot this, I'd appreciate it! 
This box is a production machine, so I can't kill it too often, but if 
anyone has ideas, I can set up another machine with a Madwifi card and see 
if I can reproduce it there.

------------------------------------------------------------------------
| nate carlson | natecars at natecarlson.com | http://www.natecarlson.com |
|       depriving some poor village of its idiot since 1981            |
------------------------------------------------------------------------


More information about the Dev mailing list