Date: Sun, 12 Jul 2009 06:56:27 -0500 (CDT) From: Larry Rosenman <ler@lerctr.org> To: Lawrence Stewart <lstewart@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Is this a known issue? Message-ID: <alpine.BSF.2.00.0907120655180.5006@borg> In-Reply-To: <4A5993A6.7030205@freebsd.org> References: <6adb930b24382e32582fca4841f91765.squirrel@webmail.lerctr.org> <4A5993A6.7030205@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Jul 2009, Lawrence Stewart wrote: > Larry Rosenman wrote: >> Got this lovely textdump tonight with -CURRENT from earlier today: >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0x318 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0xffffffff803200fe >> stack pointer = 0x28:0xffffff81d22105f0 >> frame pointer = 0x28:0xffffff81d2210610 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 1611 (bacula-fd) >> trap number = 12 >> panic: page fault >> cpuid = 1 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a >> panic() at panic+0x182 >> trap_fatal() at trap_fatal+0x2ad >> trap_pfault() at trap_pfault+0x294 >> trap() at trap+0x187 >> calltrap() at calltrap+0x8 >> --- trap 0xc, rip = 0xffffffff803200fe, rsp = 0xffffff81d22105f0, rbp = >> 0xffffff81d2210610 --- >> _mtx_lock_sleep() at _mtx_lock_sleep+0x4e >> netisr_queue_internal() at netisr_queue_internal+0xe1 >> netisr_queue_src() at netisr_queue_src+0x3c >> if_simloop() at if_simloop+0xb6 >> looutput() at looutput+0x84 >> ip_output() at ip_output+0xb88 >> tcp_output() at tcp_output+0xac9 >> tcp_usr_send() at tcp_usr_send+0x3a4 >> sosend_generic() at sosend_generic+0x3f6 >> soo_write() at soo_write+0x37 >> dofilewrite() at dofilewrite+0x85 >> kern_writev() at kern_writev+0x60 >> write() at write+0x55 >> syscall() at syscall+0x246 >> Xfast_syscall() at Xfast_syscall+0xe1 >> --- syscall (4, FreeBSD ELF64, write), rip = 0x801a0ff9c, rsp = >> 0x7fffff9fd2b8, rbp = 0x801d44e28 --- >> Uptime: 6m22s >> # >> >> Is this a known issue? >> >> Also, it appears it had just reset without trace (the 6m22s uptime is >> telltale). > > Currently being investigated. See "ppp triggers GPF panic" and "Re: r194546 > amd64: kernel panic in tcp_sack.c" for other threads on freebsd-current@ that > likely are the same panic (not confirmed yet though as we only have access to > Kamigishi's crash dumps so far). > > Do you have a crash dump? Nope, it doesn't seem to want to generate the dump, just the text dump :( (I'm on ZFS for most of my disk, with a 4GB swap, but 16GB mem). Per the later mails, I'll update to latest HEAD and cut a new kernel. > > Cheers, > Lawrence > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0907120655180.5006>