From owner-freebsd-current@FreeBSD.ORG Mon Aug 5 16:45:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E9271E2E; Mon, 5 Aug 2013 16:45:42 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-bk0-x234.google.com (mail-bk0-x234.google.com [IPv6:2a00:1450:4008:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B98D275B; Mon, 5 Aug 2013 16:45:42 +0000 (UTC) Received: by mail-bk0-f52.google.com with SMTP id e11so1046440bkh.39 for ; Mon, 05 Aug 2013 09:45:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; bh=76zv+e1Dv2GI/7SduBrzsX8Xmr6QHbaR3iBuoL7UjxA=; b=jiEcTeFGN6I5lOZulty95x3pSRJtS6dF5rd2v9mi6d7EM9tCJttdNTc8/n+ufJFJoW xFxtzwrv7CESPoTw/+NDwum4FoG6oY2TPPK7DDRD2eRzzJ8nnwQznK80+joswLTANj2b iEH5EnexsId15iyjygfrSornqREzGjy6Y+c8keOrHvW2k4PnqtkROUnM+10L/0+8QxS0 z3rRQxqaB6egC3vpVUSNJ15YQ8GyVKxFQg0v9ELiAfCJW1+/q+9e6eCTV/Ul/JQi8Ado WB/0frIfiqJoFnrpHyau+cUKc1u9uS63IkWyjG9i9723O4XJo4Si9AsoX/uYP424wBno WXSw== X-Received: by 10.205.47.73 with SMTP id ur9mr1095210bkb.156.1375721139617; Mon, 05 Aug 2013 09:45:39 -0700 (PDT) Received: from ernst.home (p4FCA7969.dip0.t-ipconnect.de. [79.202.121.105]) by mx.google.com with ESMTPSA id if11sm5172301bkc.15.2013.08.05.09.45.37 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 05 Aug 2013 09:45:38 -0700 (PDT) Date: Mon, 5 Aug 2013 18:45:36 +0200 From: Gary Jennejohn To: "Sam Fourman Jr." Subject: Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918 Message-ID: <20130805184536.33236d7b@ernst.home> In-Reply-To: References: X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.17; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Craig Rodrigues , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 16:45:43 -0000 On Sun, 4 Aug 2013 18:59:56 -0400 "Sam Fourman Jr." wrote: > 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? > kldstat -v maybe? Seems to list every module in the kernel. I don't have VIMAGE enabled so can't say whether it will really appear. -- Gary Jennejohn