From owner-freebsd-current@FreeBSD.ORG Sun Aug 4 22:52:11 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 2F49E1F6 for ; Sun, 4 Aug 2013 22:52:11 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8DE442CEC for ; Sun, 4 Aug 2013 22:52:10 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id ep20so1581527lab.2 for ; Sun, 04 Aug 2013 15:52:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qcCf0OJnHmbE7KJGocHBy8n2UFqWnLA97jCXRJJeZI0=; b=NMSyZxR6O741MnWGkUHHvdyl6JNlhYRVsJh0ij6Te/aFDJkBDui/2kXsPH0/XYF28i rgXvT2yHIb2KNzMMhuNTJRAOEL8lVWyeNNavidMD4UfRiLFm6bv59qJAsuwNCWTNaNfK rnziHF++poHrWqJrYaxEuBItPg8xt5eCXDkWQG0d3kUECWBxzoyPmqFxhi6Sk4CrE3dl rDmU1E8tteKjMwEE4T74OK90upvs+cUVUh8/lmZRpURPcnI+W38/jat4pe4pXk/Kq0O/ fl7qk+Y2hnsCkHUyY+gYU70WRWNSKjTVo06OeMH8OY1P2uAuwvAr6wsIC6FacVrsGqAX s4JQ== MIME-Version: 1.0 X-Received: by 10.112.20.137 with SMTP id n9mr7746455lbe.20.1375656728340; Sun, 04 Aug 2013 15:52:08 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.22.100 with HTTP; Sun, 4 Aug 2013 15:52:08 -0700 (PDT) In-Reply-To: References: Date: Sun, 4 Aug 2013 15:52:08 -0700 X-Google-Sender-Auth: 9JF1fC-ZJlpNVpUcoG7fNZyokiU Message-ID: Subject: Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918 From: Craig Rodrigues To: "Sam Fourman Jr." 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:52:11 -0000 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= 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: (1) Download John's gdb scripts from: http://people.freebsd.org/~jhb/gdb/ . Put them in a directory such as $HOME/gdb/ (2) Go to the kernel source directory. You must be in this directory for the gdb macros to work: cd /usr/src (3) Start kgdb: kgdb /usr/obj/sys/conf/GENERIC/kernel.debug /var/crash/vmcore [ tune that line to where your kernel.debug is ] (4) Load the gdb scripts: source /home/mydir/gdb/gdb6 (5) Go to the frame where the problem occurred. For you it is in frame 7 in6_tmpaddrtimer.c (kgdb) frame 7 (6) Find the thread id of the active thread using this: (kgdb) i thr There will be an asterisk besides the active thread such as: * 301 Thread 100515 (PID=551: at-spi-bus-launcher) 0xffffffff8094fdc6 in sched_switch (td=0xfffffe0009f43000, newtd=, (7) Using the thread id obtain in step 6, look up the value of curthread, and assign it to the $td variable, for example: (kgdb) lookup_thread 301 $td 0 (8) Print out the value of $td and derference it just like any other gdb variable (kgdb) p $td (9) Print out the value of td->td_vnet (kgdb) p $td->td_vnet I suspect td_vnet is NULL, but please confirm. -- Craig