Date: Mon, 1 Oct 2012 09:08:30 -0400 From: Kim Culhan <w8hdkim@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: panic possibly on on bridge member removal Message-ID: <CAKZxVQWFKBD3Q3uMMr94aMZgckHhu-MPzC1WiQpoNR%2BsuOWi1Q@mail.gmail.com> In-Reply-To: <201210010804.08925.jhb@freebsd.org> References: <CAKZxVQU0azfJShEiRgjsCu2aRqcBFi1qV7HDajFY2y=Dz084Gw@mail.gmail.com> <201210010804.08925.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 1, 2012 at 8:04 AM, John Baldwin <jhb@freebsd.org> wrote: > On Saturday, September 29, 2012 8:40:03 am Kim Culhan wrote: >> After a few hours of operation involving tap0 added to the bridge >> running openvpn >> and shutting down openvpn which removes tap0 from the bridge, the >> machine is found to have a panic: >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0x188 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0xffffffff82a14f96 >> stack pointer = 0x28:0xffffff8000285670 >> frame pointer = 0x28:0xffffff80002856b0 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 12 (swi5: fast taskq) >> [ thread pid 12 tid 100022 ] >> Stopped at bridge_enqueue+0x86: calll *0x188(%r12) >> db> bt >> Tracing pid 12 tid 100022 td 0xfffffe0003aff000 >> bridge_enqueue() at bridge_enqueue+0x86 > > Can you run 'gdb /boot/kernel/kernel' and do 'l *bridge_enqueue+0x86'? > > -- > John Baldwin (gdb) l *bridge_enqueue+0x86 No symbol "bridge_enqueue" in current context. (gdb) -- -kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKZxVQWFKBD3Q3uMMr94aMZgckHhu-MPzC1WiQpoNR%2BsuOWi1Q>