From owner-freebsd-current@FreeBSD.ORG Fri Dec 16 23:15:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03B1616A420; Fri, 16 Dec 2005 23:15:17 +0000 (GMT) (envelope-from antoine@peanut.dreadbsd.org) Received: from barton.dreadbsd.org (peanut.dreadbsd.org [82.67.196.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38E6243D62; Fri, 16 Dec 2005 23:15:11 +0000 (GMT) (envelope-from antoine@peanut.dreadbsd.org) Received: from barton.dreadbsd.org (localhost [127.0.0.1]) by barton.dreadbsd.org (8.13.4/8.13.4) with ESMTP id jBGNF8vq024550; Sat, 17 Dec 2005 00:15:08 +0100 (CET) (envelope-from antoine@peanut.dreadbsd.org) Received: (from antoine@localhost) by barton.dreadbsd.org (8.13.4/8.13.1/Submit) id jBGNF7wo024549; Sat, 17 Dec 2005 00:15:07 +0100 (CET) (envelope-from antoine) Date: Sat, 17 Dec 2005 00:15:07 +0100 From: Antoine Brodin To: John Baldwin Message-Id: <20051217001507.71b04041.antoine.brodin@laposte.net> In-Reply-To: <200512161525.12656.jhb@freebsd.org> References: <200512151356.41550.jhb@freebsd.org> <200512161525.12656.jhb@freebsd.org> X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, ggajic@afrodita.rcub.bg.ac.yu Subject: Re: skype-1.2.0.18-static for linux and FreeBSD 7.0 CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 16 Dec 2005 23:15:17 -0000 John Baldwin wrote: > On Friday 16 December 2005 04:13 am, Goran Gajic wrote: > > On Thu, 15 Dec 2005, John Baldwin wrote: > > > If you are in X this is probably a panic (currently the kernel doesn't > > > create a coredump while you are in X which is a bug). Can you hook up a > > > serial console and use that to get the panic message? > > > > Yes, here is capture from minicom: > > > > drm0: port 0xc000-0xc0ff mem > > 0xe8000000-0xefffffff,0xff8f0000-0xff8fffff irq 16 at device 0.0 on pci1 > > info: [drm] AGP at 0xf8000000 64MB > > info: [drm] Initialized radeon 1.19.0 20050911 > > info: [drm] Loading R200 Microcode > > lock order reversal: > > 1st 0xc366e21c vnode interlock (vnode interlock) @ kern/vfs_vnops.c:791 > > 2nd 0xc3b8fb44 process lock (process lock) @ i386/i386/trap.c:742 > > KDB: stack backtrace: > > kdb_backtrace(0,ffffffff,c0975450,c0975900,c0927544) at kdb_backtrace+0x29 > > witness_checkorder(c3b8fb44,9,c08be5a5,2e6) at witness_checkorder+0x580 > > _mtx_lock_flags(c3b8fb44,0,c08be59c,2e6,c3b91780) at _mtx_lock_flags+0x5b > > trap_pfault(dbc9da28,0,3) at trap_pfault+0xb2 > > trap(dbc90008,c0680028,c09b0028,c3b91780,dbc9da84) at trap+0x3cd > > calltrap() at calltrap+0x5 > > --- trap 0xc, eip = 0xc081799c, esp = 0xdbc9da68, ebp = 0xdbc9da70 --- > > stack_save(dbc9da84) at stack_save+0x1c > > Ah, I think the stack_save() stuff in 6.0 is buggy. I think there's a fix in > HEAD. I would just turn those DEBUG options off for now. Hi, Could you try the patch at : http://bsd.miki.eu.org/~antoine/stack/stack-12-16.diff Cheers, Antoine