From owner-freebsd-current@FreeBSD.ORG Sun Aug 4 22:59:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F268C433; Sun, 4 Aug 2013 22:59:57 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-vb0-x22e.google.com (mail-vb0-x22e.google.com [IPv6:2607:f8b0:400c:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9E61A2D47; Sun, 4 Aug 2013 22:59:57 +0000 (UTC) Received: by mail-vb0-f46.google.com with SMTP id p13so2194757vbe.5 for ; Sun, 04 Aug 2013 15:59:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=grhjmaP2yzCtM6Kdp4NZ3y8IBBD3mYr6E8Zasd/RInw=; b=gKn5F2T9zXOhzkwZ2tvnJI32+F/TJRBaM7xuAErpmtaEIMW9RC4E6Zpi1nDxDLfHvw pff6j25FfRZ8Mi4liMA0llaiEGifScC8N97MLjWgV/qHlfewcZk81TcJpOPg4XQdDJDg 4VXn0/IQhQwQPdBPSXekuQeFtsV0CTcJVPcemPLqJ/KRafVLRPdd5u3TsgB6iwmvPOA1 YUeJDu8d1vV07HoIUm/ICk/pTpZvskzOQgANBBeNkofs6GLjwvvkpIMMcF1Vn4WxjfcK uhWnuJq+16QYPknEqeiBE98c3Ftcthv/5kTt0gzbN36R33N1XDENjQUL1yetz/pAH9cc d4cg== MIME-Version: 1.0 X-Received: by 10.52.165.239 with SMTP id zb15mr4133269vdb.44.1375657196649; Sun, 04 Aug 2013 15:59:56 -0700 (PDT) Received: by 10.220.96.78 with HTTP; Sun, 4 Aug 2013 15:59:56 -0700 (PDT) In-Reply-To: References: Date: Sun, 4 Aug 2013 18:59:56 -0400 Message-ID: Subject: Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918 From: "Sam Fourman Jr." To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 22:59:58 -0000 On Sun, Aug 4, 2013 at 6:52 PM, Craig Rodrigues wrote: > On Sun, Aug 4, 2013 at 12:33 PM, Sam Fourman Jr. 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=> 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=) at >> /usr/src/sys/kern/kern_timeout.c:802 >> #10 0xffffffff80815dc3 in intr_event_execute_handlers (p=> 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 >> , 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.