panic in recent 6-current
John Baldwin
jhb at FreeBSD.org
Tue Feb 8 18:32:28 GMT 2005
On Tuesday 08 February 2005 12:27 pm, Divacky Roman wrote:
> On Tue, Feb 08, 2005 at 08:47:11AM -0800, Kris Kennaway wrote:
> > On Tue, Feb 08, 2005 at 03:04:19PM +0100, Divacky Roman wrote:
> > > #22 0xc0493087 in softclock (dummy=0x0) at atomic.h:365
> > > #23 0xc04768a3 in ithread_loop (arg=0xc1577480)
> > > at /usr/src/sys/kern/kern_intr.c:546
> > > #24 0xc0475be9 in fork_exit (callout=0xc0476761 <ithread_loop>,
> > > arg=0xc1577480, frame=0xd3fc3d48) at
> > > /usr/src/sys/kern/kern_fork.c:790 #25 0xc057ef5c in fork_trampoline ()
> > > at /usr/src/sys/i386/i386/exception.s:208
> > >
> > >
> > > (all other frames are either ??? or from ddb)
> >
> > Are you running a kernel built with -O2 (bad for gdb) or -O?
>
> -Os which is basically -O2, should I test with plain -O ?
-Os also confuses ddb's strack tracer, just stick to -O. Also, you didn't
supply the actual panic message.
--
John Baldwin <jhb at FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
More information about the freebsd-current
mailing list