Re: odd panics on -current recently

On Sat, 18 Jun 2005, Wesley Morgan wrote:

> Been getting what appear to be the same panic for at least a week on
> -current. Enabled dumps and this is the best trace I can get. I don't have
> the panic message, and this trace doesn't make a lot of sense to me:
>
> #0  doadump () at pcpu.h:165
> 165             __asm __volatile("movl %%fs:0,%0" : "=r" (td));
> (kgdb) bt
> #0  doadump () at pcpu.h:165
> #1  0xc0706e40 in buf.1 ()
> #2  0xc051bfee in boot (howto=260) at ../../../kern/kern_shutdown.c:397
> #3  0xc051c416 in panic (fmt=0xc06b19aa "%s")
>      at ../../../kern/kern_shutdown.c:553
> #4  0xc0688e6c in trap_fatal (frame=0xd3c1dc40, eva=0)
>      at ../../../i386/i386/trap.c:831
> #5  0xc06883a9 in trap (frame=
>        {tf_fs = -1068302328, tf_es = -1066401752, tf_ds = -1047068632,
> tf_edi = -1047265920, tf_esi = -1035014144, tf_ebp = 0, tf_isp =
> -742269844, tf_ebx = -1066355360, tf_edx = -1035014144, tf_ecx = 0, tf_eax
> = -2, tf_trapno = 12, tf_err = 0, tf_eip = -1068198526, tf_cs = 32,
> tf_eflags = 589954, tf_esp = -1035014144, tf_ss = 4}) at
> ../../../i386/i386/trap.c:269
> #6  0xc067674a in calltrap () at ../../../i386/i386/exception.s:139
> (kgdb)

You didn't post the panic message, which is necessary to determine why the
trap occured in the first place, and there appears to be a lot of missing
backtrace since you can't get to trap_fatal from a userspace trap.

You might also derive a kernel config from GENERIC instead of LINT so you
don't include some of the more esoteric options and trigger uncommonly
used code paths.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite_at_gumbysoft.com          |  www.FreeBSD.org