Modify ↓
Opened 7 years ago
Closed 6 years ago
#9660 closed defect (no_response)
Combination b43 and ipsec causes increased load and makes dropbear connections stuck
Reported by: | q0081@… | Owned by: | developers |
---|---|---|---|
Priority: | response-needed | Milestone: | Backfire 10.03.1 |
Component: | kernel | Version: | Backfire 10.03.1 RC4 |
Keywords: | b43 ipsec dropbear | Cc: |
Description
System: wrt54gs rev 1.1
Firmware: 10.03.1-rc4 brcm47xx
Wireless is off. But when i start ipsec, sysload gets continously up, all dropbear ssh connection are stuck.
Kernel log says:
... NET: Unregistered protocol family 15 klips_info:ipsec_init: KLIPS startup, Openswan KLIPS IPsec stack version: 2.6.29 NET: Registered protocol family 15 registered KLIPS /proc/sys/net klips_info:ipsec_alg_init: KLIPS alg v=0.8.1-0 (EALG_MAX=255, AALG_MAX=251) klips_info:ipsec_alg_init: calling ipsec_alg_static_init() ipsec_aes_init(alg_type=15 alg_id=12 name=aes): ret=0 klips_debug: experimental ipsec_alg_AES_MAC not registered [Ok] (auth_id=0) ipsec_3des_init(alg_type=15 alg_id=3 name=3des): ret=0 b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY CPU 0 Unable to handle kernel paging request at virtual address 00000000, epc == 800913a4, ra == 80091714 Oops[#1]: Cpu 0 $ 0 : 00000000 1000a800 08800076 00000000 $ 4 : 00000000 8101de80 80ef4e4c 80ef4040 $ 8 : 81a4fa00 0000a800 00000000 8028e000 $12 : 7fab8e50 00000000 0bb7f99a 00430000 $16 : 81a35790 00000000 818c4300 00000001 $20 : 802e0000 80000000 818c4348 00100100 $24 : 00000000 801ea7d0 $28 : 81822000 81823e08 00200200 80091714 Hi : 0000002e Lo : 66666672 epc : 800913a4 0x800913a4 Not tainted ra : 80091714 0x80091714 Status: 1000a802 KERNEL EXL Cause : 0080000c BadVA : 00000000 PrId : 00029007 (Broadcom BCM3302) Modules linked in: ipsec ip6t_REJECT ip6t_LOG ip6t_rt ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah ip6table_raw ip6_queue ip6table_mangle ip6table_filter ip6_tables nf_conntrack_ipv6 nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables sit ppp_mppe tunnel4 ppp_async xfrm_ipcomp b43legacy b43 mac80211 pppoe pppox ppp_generic slhc crc_ccitt cfg80211 compat_firmware_class compat sha1_generic md5 hmac des_generic arc4 aes_generic deflate ecb cbc ipv6 switch_robo switch_core diag [last unloaded: af_key] Process events/0 (pid: 4, threadinfo=81822000, task=81820958, tls=00000000) Stack : 00000005 818420c0 818420b8 80292f58 81a35790 81a35780 00000001 802ddb44 802987a8 802a0000 fffffffe efffffff 8025dec4 80091714 80292f28 8001cef8 80290000 8024ac68 81a4fa00 818c4300 80290000 80091904 8025dec4 8015e36c 00000002 00000001 00000000 81802a88 81823ea8 81802a80 81802a88 81823ea8 fffffffc 802ce8c0 00010000 80039740 00000000 80250000 81813938 81820958 ... Call Trace:[<80091714>] 0x80091714 [<8001cef8>] 0x8001cef8 [<80091904>] 0x80091904 [<8015e36c>] 0x8015e36c [<80039740>] 0x80039740 [<8003e1ec>] 0x8003e1ec [<80039568>] 0x80039568 [<8003db30>] 0x8003db30 [<8000f86c>] 0x8000f86c [<8003dab4>] 0x8003dab4 [<8000f85c>] 0x8000f85c Code: 8ec80004 8ce30004 8ce20000 <ac620000> ac430004 acf70000 acfe0004 8ce4000c 8e420014 Disabling lock debugging due to kernel taint b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY b44: eth0: powering down PHY ...
Attachments (0)
Change History (2)
comment:1 Changed 7 years ago by jow
- Priority changed from high to response-needed
comment:2 Changed 6 years ago by nbd
- Resolution set to no_response
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Is this still the case with RC5 ?