From owner-freebsd-stable@FreeBSD.ORG Sat Nov 11 08:36:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B801D16A40F for ; Sat, 11 Nov 2006 08:36:30 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 394F243D49 for ; Sat, 11 Nov 2006 08:36:30 +0000 (GMT) (envelope-from max@love2party.net) Received: from [81.74.42.155] (helo=[192.168.99.198]) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis), id 0ML25U-1GioLk2Qnn-000881; Sat, 11 Nov 2006 09:36:29 +0100 From: Max Laier To: freebsd-stable@freebsd.org Date: Sat, 11 Nov 2006 09:36:18 +0100 User-Agent: KMail/1.9.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611110936.19397.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Scott Ullrich Subject: Re: Panic while starting OpenNTPD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2006 08:36:30 -0000 Hey Scott, On Saturday 11 November 2006 04:44, Scott Ullrich wrote: > Sources from today, right before the compile. > > I have paused the virtual machine if someone would like me to issue > further db> commands. > > Thanks, > > Scott > > > FreeBSD 6.2-PRERELEASE #0: Sat Nov 11 02:47:35 UTC 2006 > sullrich@builder.livebsd.com:/usr/obj.pfSense/usr/src/sys/pfSense_Dev.6 > > lock order reversal: (sleepable after non-sleepable) > 1st 0xc0a57000 pf task mtx (pf task mtx) @ > /usr/src/sys/contrib/pf/net/pf.c:6406 > 2nd 0xc0a787e4 user map (user map) @ /usr/src/sys/vm/vm_map.c:3074 This one we can ignore - it's a double fault artefact. > KDB: stack backtrace: > kdb_backtrace(0,ffffffff,c0b59f08,c0b5b740,c0a03b2c,...) at > kdb_backtrace+0x29 witness_checkorder(c0a787e4,9,c09a1f59,c02) at > witness_checkorder+0x578 _sx_xlock(c0a787e4,c09a1f59,c02) at _sx_xlock+0x50 > _vm_map_lock_read(c0a787a0,c09a1f59,c02,18e17c0,c25846b0,...) at > _vm_map_lock_read+0x37 > vm_map_lookup(cc1c4a4c,0,1,cc1c4a50,cc1c4a40,cc1c4a44,cc1c4a27,cc1c4a28) > atvm_m ap_lookup+0x28 > vm_fault(c0a787a0,0,1,0,c2585a80,...) at vm_fault+0x66 > trap(cc1c4b14,0,104) at trap+0x65e > trap(8,28,28,c27432c4,c26aee00,...) at trap+0x341 > alltraps(1,c274e400,cc1c4c5c,0,0) at alltraps+0x1a > pfioctl(0,cc1c4c5c,c274e400,1,0) at pfioctl+0x3dd7 > pfil_run_hooks(c0b9c720,cc1c4cb0,c274e400,1,0) at pfil_run_hooks+0xc9 > ip_input(c2743200) at ip_input+0x274 > netisr_unregister(c0b99f78) at netisr_unregister+0x11e > netisr_queue(0) at netisr_queue+0x146 > ithread_destroy(c2584648,c25af480) at ithread_destroy+0xf6 > ithread_destroy(c25648c0,cc1c4d38,c25648c0,c06b4b5c,0,...) at > ithread_destroy+0x21b > fork_exit(c06b4b5c,c25648c0,cc1c4d38) at fork_exit+0xd0 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xcc1c4d6c, ebp = 0 --- > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x104 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0489090 > stack pointer = 0x28:0xcc1c4b54 > frame pointer = 0x28:0xcc1c4c1c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 13 (swi1: net) > [thread pid 13 tid 100003 ] > Stopped at pf_test+0x968: cmpl $0,0x104(%eax) > db> bt > Tracing pid 13 tid 100003 td 0xc2585a80 > pf_test(1,c274e400,cc1c4c5c,0,0) at pf_test+0x968 > pfioctl(0,cc1c4c5c,c274e400,1,0) at pfioctl+0x3dd7 > pfil_run_hooks(c0b9c720,cc1c4cb0,c274e400,1,0) at pfil_run_hooks+0xc9 This part of the trace is *very* strange. I don't see how pfil would call to pfioctl. Can you get line numbers for pfioctl+0x3dd7 and pf_test+0x968 ? "ps" would also be helpful. Thanks. > ip_input(c2743200) at ip_input+0x274 > netisr_unregister(c0b99f78) at netisr_unregister+0x11e > netisr_queue(0) at netisr_queue+0x146 > ithread_destroy(c2584648,c25af480) at ithread_destroy+0xf6 > ithread_destroy(c25648c0,cc1c4d38,c25648c0,c06b4b5c,0,...) at > ithread_destroy+0x21b > fork_exit(c06b4b5c,c25648c0,cc1c4d38) at fork_exit+0xd0 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xcc1c4d6c, ebp = 0 --- > db> -- Max