OpenWrt Forum Archive

Topic: openvpn --mktun --dev tap0 causes Segmentation fault

The content of this topic has been archived on 28 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi all,

I'm trying to run OpenVPN on experimental/whiterussian, but I get Segmentation faults.

root@osm_fw:~# insmod tun
Using /lib/modules/2.4.30/tun.o
root@osm_fw:~# openvpn --mktun --dev tap0
Thu Jul 28 12:41:24 2005 TUN/TAP device tap0 opened
Segmentation fault

I think, everybody has to have this problem on wrt54gs, or am I wrong?

Thanks for any comments

Marek Drapal

--


Jul 28 12:41:11 (none) kern.info kernel: Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
Jul 28 12:41:24 (none) kern.alert kernel: Unable to handle kernel paging request at virtual address 52cf4a14, epc == 8002d3d4, ra == 80051964
Jul 28 12:41:24 (none) kern.warn kernel: Oops in fault.c::do_page_fault, line 206:
Jul 28 12:41:24 (none) kern.warn kernel: $0 : 00000000 1000fc00 00000060 8100001c 8105bdd4 00000004 52cf4a08 8105bdd4
Jul 28 12:41:24 (none) kern.warn kernel: $8 : 8105bde4 1000fc01 fffffff7 00000001 2ad957b4 006ca5ac 00000000 00413470
Jul 28 12:41:24 (none) kern.warn kernel: $16: 0000000f 81e25000 81913220 81b1ccc0 00000000 00000000 00000000 1000811c
Jul 28 12:41:24 (none) kern.warn kernel: $24: 0000002a 2ade9660   819b2000 819b3e88 1000815c 80051964
Jul 28 12:41:24 (none) kern.warn kernel: Hi : 0000004c
Jul 28 12:41:24 (none) kern.warn kernel: Lo : 019ffd65
Jul 28 12:41:24 (none) kern.warn kernel: epc   : 8002d3d4    Tainted: P
Jul 28 12:41:24 (none) kern.warn kernel: Status: 1000fc02
Jul 28 12:41:24 (none) kern.warn kernel: Cause : 00000008
Jul 28 12:41:24 (none) kern.warn kernel: PrId  : 00029007
Jul 28 12:41:24 (none) kern.warn kernel: Process openvpn (pid: 1077, stackpage=819b2000)
Jul 28 12:41:24 (none) kern.warn kernel: Stack:    81913400 80050c18 81913528 00030002 81bb8c00 00000000 80051ac8
Jul 28 12:41:24 (none) kern.warn kernel:  81b1cd58 81913400 8004d70c 81913400 800c7274 81e25000 00008943 81bb8ba0
Jul 28 12:41:24 (none) kern.warn kernel:  80216460 800377d0 800377f0 00000693 00000001 fffffff7 00000003 81bb8ba0
Jul 28 12:41:24 (none) kern.warn kernel:  81ecad60 00000000 00000001 80036298 80036290 800486d4 81bb8ba0 80047d9c
Jul 28 12:41:24 (none) kern.warn kernel:  00000000 1000bae8 7fff7f57 00000000 80036350 800454cb 00000003 00000000
Jul 28 12:41:24 (none) kern.warn kernel:  00000001 ...
Jul 28 12:41:24 (none) kern.warn kernel: Call Trace:   [<80050c18>] [<80051ac8>] [<8004d70c>] [<800c7274>] [<800377d0>]
Jul 28 12:41:24 (none) kern.warn kernel:  [<800377f0>] [<80036298>] [<80036290>] [<800486d4>] [<80047d9c>] [<80036350>]
Jul 28 12:41:24 (none) kern.warn kernel:  [<800454cb>] [<800084a0>] [<800084a0>] [<800454cb>]
Jul 28 12:41:24 (none) kern.warn kernel:
Jul 28 12:41:24 (none) kern.warn kernel: Code: 00431021  8c460004  8c820018 <8cc3000c> 14400002  00000000  000001cd  8cc40014  00a32823

can you please update to whiterussian rc2 and report if this problem still exist?

I did exactly that today using rc2 without any problems.

The discussion might have continued from here.