Date: Sat, 26 Aug 2006 09:49:36 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Fatal trap 30 when loading if_xl Message-ID: <20060826004936.GA31324@cdnetworks.co.kr> In-Reply-To: <200608251012.42642.jhb@freebsd.org> References: <20060819211853.GA1016@tin.it> <200608251012.42642.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 25, 2006 at 10:12:42AM -0400, John Baldwin wrote: > On Saturday 19 August 2006 17:18, Paolo Pisati wrote: > > Today's CURRENT panic my box everytime i load > > if_xl: > > > > [flag@newluxor NEWLUXOR]$ sudo kgdb kernel.debug /var/crash/vmcore.0 > > [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > > GNU gdb 6.1.1 [FreeBSD] > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "i386-marcel-freebsd". > > 30 (unknown trap) can mean that you got a device interrupt to an IDT > entry you haven't installed a handler for yet. If you want to figure > out exactly which IDT entry, you'll need to install a unique custom > dummy handler in each IDT entry so you can tell which one fired. > After bring up to date CURRENT I see this panic too while loading if_em which used to work flawlessly. -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060826004936.GA31324>