Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
I forgot to mention, sysctl kern.conftxt > will only display something if you have this in your kernel config: > > options INCLUDE_CONFIG_FILE # Include this file in kernel > > It's always handy to have that in your kernel config. > > -- > Craig > No wonder why, it wasn't working for me and I didn't know why -- Sam Fourman Jr. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
On Mon, Aug 5, 2013 at 10:53 PM, Gary Jennejohn wrote: > On Mon, 5 Aug 2013 10:29:23 -0700 > Craig Rodrigues wrote: > > > > > On the booted an running system, if you type: > > > > sysctl kern.conftxt > > > > that will display the actual kernel config options used to build the > > running kernel. > > > > Not necessarily > > sysctl kern.conftxt > sysctl: unknown oid 'kern.conftxt': No such file or directory > I forgot to mention, sysctl kern.conftxt will only display something if you have this in your kernel config: options INCLUDE_CONFIG_FILE # Include this file in kernel It's always handy to have that in your kernel config. -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
On Mon, 5 Aug 2013 10:29:23 -0700 Craig Rodrigues wrote: > On Sun, Aug 4, 2013 at 3:59 PM, Sam Fourman Jr. wrote: > > > > > > > > > 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? > > > > On the booted an running system, if you type: > > sysctl kern.conftxt > > that will display the actual kernel config options used to build the > running kernel. > Not necessarily sysctl kern.conftxt sysctl: unknown oid 'kern.conftxt': No such file or directory -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
On Sun, Aug 4, 2013 at 3:59 PM, Sam Fourman Jr. wrote: > > > > 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? > On the booted an running system, if you type: sysctl kern.conftxt that will display the actual kernel config options used to build the running kernel. This is handy because once or twice when doing development, I edited a kernel config file and forgot to rebuild the kernel before installing it. It would still be useful if you could run through those steps which I gave you and provide the debugging output, just to double check. -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
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 0x80bd6027 in trap_pfault (frame=0x0, usermode= >> optimized > >> out>) at /usr/src/sys/amd64/amd64/trap.c:699 > >> #5 0x80bd5876 in trap (frame=0xff80002787c0) at > >> /usr/src/sys/amd64/amd64/trap.c:463 > >> #6 0x80bc06b2 in calltrap () at > >> /usr/src/sys/amd64/amd64/exception.S:232 > >> #7 0x809937a8 in in6_tmpaddrtimer (arg=0xfe00170fc0b6) at > >> /usr/src/sys/netinet6/in6_ifattach.c:935 > >> #8 0x8085140a in softclock_call_cc (c=0x81325210, > >> cc=0x8131c700, direct=0) at /usr/src/sys/kern/kern_timeout.c:674 > >> #9 0x80851704 in softclock (arg=) at > >> /usr/src/sys/kern/kern_timeout.c:802 > >> #10 0x80815dc3 in intr_event_execute_handlers (p= >> out>, ie=0xfe0014ab3400) at /usr/src/sys/kern/kern_intr.c:1263 > >> #11 0x80816716 in ithread_loop (arg=0xfe0014a896e0) at > >> /usr/src/sys/kern/kern_intr.c:1276 > >> #12 0x80813b31 in fork_exit (callout=0x80816680 > >> , arg=0xfe0014a896e0, frame=0xff8000278a40) at > >> /usr/src/sys/kern/kern_fork.c:991 > >> #13 0x80bc0bee in fork_trampoline () at > >> /usr/src/sys/amd64/amd64/exception.S:606 > >> #14 0x 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
> Can you try to update the kernel to r253950 or later? This is > probably because one of my recent commits broke IPv6 temporary > address timer on non-IPv6 interfaces. > > -- Hiroki > I just built a kernel based on r253950, I will keep the list updated if the panic happens again -- Sam Fourman Jr. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
"Sam Fourman Jr." wrote in : sf> could someone help me figure out why this machine kernel paniced? sf> I have a full crashdump file if needed, sf> this machine is configured as a Firewall and wifi hostap running pf in a sf> small office ... sf> #7 0x809937a8 in in6_tmpaddrtimer (arg=0xfe00170fc0b6) at sf> /usr/src/sys/netinet6/in6_ifattach.c:935 sf> #8 0x8085140a in softclock_call_cc (c=0x81325210, sf> cc=0x8131c700, direct=0) at /usr/src/sys/kern/kern_timeout.c:674 Can you try to update the kernel to r253950 or later? This is probably because one of my recent commits broke IPv6 temporary address timer on non-IPv6 interfaces. -- Hiroki pgpSizRfnM0Ys.pgp Description: PGP signature
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
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 0x80bd6027 in trap_pfault (frame=0x0, usermode=> optimized >> out>) at /usr/src/sys/amd64/amd64/trap.c:699 >> #5 0x80bd5876 in trap (frame=0xff80002787c0) at >> /usr/src/sys/amd64/amd64/trap.c:463 >> #6 0x80bc06b2 in calltrap () at >> /usr/src/sys/amd64/amd64/exception.S:232 >> #7 0x809937a8 in in6_tmpaddrtimer (arg=0xfe00170fc0b6) at >> /usr/src/sys/netinet6/in6_ifattach.c:935 >> #8 0x8085140a in softclock_call_cc (c=0x81325210, >> cc=0x8131c700, direct=0) at /usr/src/sys/kern/kern_timeout.c:674 >> #9 0x80851704 in softclock (arg=) at >> /usr/src/sys/kern/kern_timeout.c:802 >> #10 0x80815dc3 in intr_event_execute_handlers (p=> out>, ie=0xfe0014ab3400) at /usr/src/sys/kern/kern_intr.c:1263 >> #11 0x80816716 in ithread_loop (arg=0xfe0014a896e0) at >> /usr/src/sys/kern/kern_intr.c:1276 >> #12 0x80813b31 in fork_exit (callout=0x80816680 >> , arg=0xfe0014a896e0, frame=0xff8000278a40) at >> /usr/src/sys/kern/kern_fork.c:991 >> #13 0x80bc0bee in fork_trampoline () at >> /usr/src/sys/amd64/amd64/exception.S:606 >> #14 0x 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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
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 0x80bd6027 in trap_pfault (frame=0x0, usermode= out>) at /usr/src/sys/amd64/amd64/trap.c:699 > #5 0x80bd5876 in trap (frame=0xff80002787c0) at > /usr/src/sys/amd64/amd64/trap.c:463 > #6 0x80bc06b2 in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:232 > #7 0x809937a8 in in6_tmpaddrtimer (arg=0xfe00170fc0b6) at > /usr/src/sys/netinet6/in6_ifattach.c:935 > #8 0x8085140a in softclock_call_cc (c=0x81325210, > cc=0x8131c700, direct=0) at /usr/src/sys/kern/kern_timeout.c:674 > #9 0x80851704 in softclock (arg=) at > /usr/src/sys/kern/kern_timeout.c:802 > #10 0x80815dc3 in intr_event_execute_handlers (p= out>, ie=0xfe0014ab3400) at /usr/src/sys/kern/kern_intr.c:1263 > #11 0x80816716 in ithread_loop (arg=0xfe0014a896e0) at > /usr/src/sys/kern/kern_intr.c:1276 > #12 0x80813b31 in fork_exit (callout=0x80816680 > , arg=0xfe0014a896e0, frame=0xff8000278a40) at > /usr/src/sys/kern/kern_fork.c:991 > #13 0x80bc0bee in fork_trampoline () at > /usr/src/sys/amd64/amd64/exception.S:606 > #14 0x 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) 0x8094fdc6 in sched_switch (td=0xfe0009f43000, 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
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 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 10 fault virtual address = 0x10 fault code = supervisor read data, page not present instruction pointer = 0x20:0x809937a8 stack pointer= 0x28:0xff8000278870 frame pointer= 0x28:0xff80002788c0 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock) trap number = 12 panic: page fault cpuid = 0 Uptime: 23h57m13s Dumping 2452 out of 8070 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% Reading symbols from /boot/kernel/zfs.ko.symbols...done. Loaded symbols for /boot/kernel/zfs.ko.symbols Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /boot/kernel/opensolaris.ko.symbols Reading symbols from /boot/kernel/uhid.ko.symbols...done. Loaded symbols for /boot/kernel/uhid.ko.symbols Reading symbols from /boot/kernel/wlan_xauth.ko.symbols...done. Loaded symbols for /boot/kernel/wlan_xauth.ko.symbols #0 doadump (textdump=1) at pcpu.h:236 236 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=1) at pcpu.h:236 #1 0x8083eb21 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:447 #2 0x8083ee84 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:754 #3 0x80bd5dea in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:873 #4 0x80bd6027 in trap_pfault (frame=0x0, usermode=) at /usr/src/sys/amd64/amd64/trap.c:699 #5 0x80bd5876 in trap (frame=0xff80002787c0) at /usr/src/sys/amd64/amd64/trap.c:463 #6 0x80bc06b2 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 #7 0x809937a8 in in6_tmpaddrtimer (arg=0xfe00170fc0b6) at /usr/src/sys/netinet6/in6_ifattach.c:935 #8 0x8085140a in softclock_call_cc (c=0x81325210, cc=0x8131c700, direct=0) at /usr/src/sys/kern/kern_timeout.c:674 #9 0x80851704 in softclock (arg=) at /usr/src/sys/kern/kern_timeout.c:802 #10 0x80815dc3 in intr_event_execute_handlers (p=, ie=0xfe0014ab3400) at /usr/src/sys/kern/kern_intr.c:1263 #11 0x80816716 in ithread_loop (arg=0xfe0014a896e0) at /usr/src/sys/kern/kern_intr.c:1276 #12 0x80813b31 in fork_exit (callout=0x80816680 , arg=0xfe0014a896e0, frame=0xff8000278a40) at /usr/src/sys/kern/kern_fork.c:991 #13 0x80bc0bee in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:606 #14 0x in ?? () Current language: auto; currently minimal (kgdb) if you need a dmesg it is below Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #1 r253918: Sat Aug 3 18:32:13 UTC 2013 root@Border:/usr/obj/usr/src/sys/BORDER amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: AMD FX(tm)-4100 Quad-Core Processor (3600.29-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x600f12 Family = 0x15 Model = 0x1 Stepping = 2 Features=0x178bfbff Features2=0x1e98220b AMD Features=0x2e500800 AMD Features2=0x1c9bfff,> TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 7868518400 (7504 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 16 cpu1 (AP): APIC ID: 17 cpu2 (AP): APIC ID: 18 cpu3 (AP): APIC ID: 19 ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has zero address or length: 0x/0x1 (20130725/tbfadt-630) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-55 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecount
