Date: Sat, 25 Jul 2015 20:15:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 201876] panic: rw lock 0xcc0bef50 not unlocked (CURRENT w/IPSEC + if_gre) Message-ID: <bug-201876-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201876 Bug ID: 201876 Summary: panic: rw lock 0xcc0bef50 not unlocked (CURRENT w/IPSEC + if_gre) Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: jason.unovitch@gmail.com The last CURRENT that has been really solid for me has been from the first week of June. The consistently reproducible issue I had earlier in bug 201642 has been fixed but I'm still running into intermittent issues. This was just seen on a recent build and I'm still working on a case to reproduce it. This is one `uname -a` FreeBSD xju-rtr 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r285871: Sat Jul 25 15:52:43 UTC 2015 root@xts-bsd:/usr/obj/nanobsd.soekris/i386.i386/usr/src/head/sys/GENERIC i386 panic: rw lock 0xcc0bef50 not unlocked cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper(c1538ae5,c1793ce8,eb7eae30,eb7ead90,c0a2a98d,...) at db_trace_self_wrapper+0x2a/frame 0xeb7ead60 kdb_backtrace(c170905b,1,c153365c,eb7eae30,1,...) at kdb_backtrace+0x2d/frame 0xeb7eadc8 vpanic(c153365c,eb7eae30,c153365c,eb7eae30,eb7eae30,...) at vpanic+0x117/frame 0xeb7eae00 kassert_panic(c153365c,cc0bef50,cc0bef00,cc0bef00,eb7eae50,...) at kassert_panic+0xe9/frame 0xeb7eae24 _rw_destroy(cc0bef60,cc0bef00,ccd9f180,eb7eae80,c0e30141,...) at _rw_destroy+0x40/frame 0xeb7eae3c ipsec_delisr(cc0bef00,c1565abd,49d,3f2,eb7eae80,...) at ipsec_delisr+0x15/frame 0xeb7eae50 _key_freesp(cc0bef4c,c1567acf,3f3,baf5ab2c,7e951cde,...) at _key_freesp+0xb1/frame 0xeb7eae80 esp_output_cb(cc658a14,41,eb7eaf38,c0e52170,cc350800,...) at esp_output_cb+0x4fc/frame 0xeb7eaf08 crypto_done(cc658a14,cc350800,fc,20,eb7eafc0,...) at crypto_done+0xa3/frame 0xeb7eaf38 swcr_process(c7197200,cc658a14,0,c23ba700,0,...) at swcr_process+0xca/frame 0xeb7eb5d0 crypto_invoke(0,0,c17d23a8,c7ea29a0,cc3e1888,...) at crypto_invoke+0x92/frame 0xeb7eb604 crypto_dispatch(cc658a14,c1567acf,363,eb7eb683,c719f888,...) at crypto_dispatch+0x78/frame 0xeb7eb620 esp_output(cc350800,cc0bef00,0,14,9,...) at esp_output+0xa03/frame 0xeb7eb6d8 ipsec4_process_packet(cc350800,cc0bef00,eb7eb870,0,ccd9f180,...) at ipsec4_process_packet+0x226/frame 0xeb7eb7d0 ip_ipsec_output(eb7eb874,0,eb7eb870,4a3e5,eb7eb8c0,...) at ip_ipsec_output+0xc9/frame 0xeb7eb7f8 ip_output(cc350800,0,0,1,0,...) at ip_output+0xb74/frame 0xeb7eb8b4 in_gre_output(cc350800,2,18,373,35b,...) at in_gre_output+0xad/frame 0xeb7eb8e0 gre_transmit(cb442c00,cc350800,4,1,2,...) at gre_transmit+0x30f/frame 0xeb7eb948 gre_output(cb442c00,cc350800,c7934bd0,eb7eb9f8,cb415000,...) at gre_output+0x1a5/frame 0xeb7eb970 ip_output(cc350800,0,0,0,0,...) at ip_output+0x18da/frame 0xeb7eba30 udp_send(c9f298e8,0,cc350800,cce47000,0,...) at udp_send+0xb97/frame 0xeb7ebaec sosend_dgram(c9f298e8,cce47000,eb7ebb70,0,0,...) at sosend_dgram+0x39a/frame 0xeb7ebb30 kern_sendit(c7e6f660,7,eb7ebbf8,0,0,...) at kern_sendit+0x298/frame 0xeb7ebba4 sendit(eb7ebbf8,0,bfbfd20a,0,cce47000,...) at sendit+0x131/frame 0xeb7ebbe0 sys_sendto(c7e6f660,eb7ebca8,c152c1b1,4,c1960a10,...) at sys_sendto+0x58/frame 0xeb7ebc18 syscall(eb7ebce8) at syscall+0x33e/frame 0xeb7ebcdc Xint0x80_syscall() at Xint0x80_syscall+0x2c/frame 0xeb7ebcdc --- syscall (133, FreeBSD ELF32, sys_sendto), eip = 0x2818ecbf, esp = 0xbfbfcf94, ebp = 0xbfbfd644 --- KDB: enter: panic [ thread pid 53412 tid 100133 ] Stopped at kdb_enter+0x3d: movl $0,kdb_why -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201876-8>