Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918

[Sam Fourman Jr.]

On Sun, Aug 4, 2013 at 6:52 PM, Craig Rodrigues <rodrigc at freebsd.org> wrote:

> On Sun, Aug 4, 2013 at 12:33 PM, Sam Fourman Jr. <sfourman at gmail.com>wrote:
>
>> hello list,
>>
>> could someone help me figure out why this machine kernel paniced?
>> I have a full crashdump file if needed,
>> this machine is configured as a Firewall and wifi hostap running pf in a
>> small office
>>
>>
>> here is a mailing list post to someone that had a similar problem a few
>> years back
>> http://lists.freebsd.org/pipermail/freebsd-bugs/2011-April/043985.html
>>
>> a backtrace, full dmesg, and kernel config are below
>>
>>
>> kgdb /boot/kernel/kernel /var/crash/vmcore.0
>> #4  0xffffffff80bd6027 in trap_pfault (frame=0x0, usermode=<value
>> optimized
>> out>) at /usr/src/sys/amd64/amd64/trap.c:699
>> #5  0xffffffff80bd5876 in trap (frame=0xffffff80002787c0) at
>> /usr/src/sys/amd64/amd64/trap.c:463
>> #6  0xffffffff80bc06b2 in calltrap () at
>> /usr/src/sys/amd64/amd64/exception.S:232
>> #7  0xffffffff809937a8 in in6_tmpaddrtimer (arg=0xfffffe00170fc0b6) at
>> /usr/src/sys/netinet6/in6_ifattach.c:935
>> #8  0xffffffff8085140a in softclock_call_cc (c=0xffffffff81325210,
>> cc=0xffffffff8131c700, direct=0) at /usr/src/sys/kern/kern_timeout.c:674
>> #9  0xffffffff80851704 in softclock (arg=<value optimized out>) at
>> /usr/src/sys/kern/kern_timeout.c:802
>> #10 0xffffffff80815dc3 in intr_event_execute_handlers (p=<value optimized
>> out>, ie=0xfffffe0014ab3400) at /usr/src/sys/kern/kern_intr.c:1263
>> #11 0xffffffff80816716 in ithread_loop (arg=0xfffffe0014a896e0) at
>> /usr/src/sys/kern/kern_intr.c:1276
>> #12 0xffffffff80813b31 in fork_exit (callout=0xffffffff80816680
>> <ithread_loop>, arg=0xfffffe0014a896e0, frame=0xffffff8000278a40) at
>> /usr/src/sys/kern/kern_fork.c:991
>> #13 0xffffffff80bc0bee in fork_trampoline () at
>> /usr/src/sys/amd64/amd64/exception.S:606
>> #14 0x0000000000000000 in ?? ()
>> Current language:  auto; currently minimal
>> (kgdb)
>>
>>
>>
>
> You have VIMAGE enabled in your kernel config.  I have debugged a few of
> these VIMAGE problems
> before.
>
> Can you do the following for me:
>
>
Craig,

Thank you for getting back to me, I will get to work on this right away and
get you what you need.
but are we CERTAIN this panic could be from VIMAGE? I totally thought I had
a # infront of that line when I built this kernel...

if you notice I did post the kernel config at the bottom of that email, and
VIMAGE is NOT included...
but maybe I did something wrong and somehow built VIMAGE in anyway..

is there some sort of command I can run to ask the system if it does indeed
have VIMAGE?
-- 

Sam Fourman Jr.