From owner-freebsd-current Thu Jan 23 0:15:39 2003 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 C36CB37B401 for ; Thu, 23 Jan 2003 00:15:37 -0800 (PST) Received: from relay8.melbpc.org.au (newglider.melbpc.org.au [203.12.152.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B41843F13 for ; Thu, 23 Jan 2003 00:15:36 -0800 (PST) (envelope-from kpeter@melbpc.org.au) Received: from melbpc.org.au (a1-86.melbpc.org.au [203.12.158.86]) by relay8.melbpc.org.au (8.12.6/8.12.6) with ESMTP id h0N8FRP5020861 for ; Thu, 23 Jan 2003 19:15:28 +1100 (EST) (envelope-from kpeter@melbpc.org.au) Message-ID: <3E2FA4A1.5020301@melbpc.org.au> Date: Thu, 23 Jan 2003 19:15:29 +1100 From: Peter Kostouros Reply-To: kpeter@melbpc.org.au Organization: Private Individual User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3a) Gecko/20021222 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: Fatal trap 12: page fault while in kernel mode References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.4(snapshot 20020706) (relay1) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I recompiled the official nv driver with debugging symbols: X works as expected. My apologies if I alarmed anyone. John Baldwin wrote: >On 22-Jan-2003 Peter Kostouros wrote: > > >>Hi >> >>I am having a similar problem to what has been reported previously >>regarding X. Basically I get a fatal trap 12. (cvsup'ed about one hour >>ago.) I have attached a backtrace I hope is useful. >> >>When I started X within gdb, I received the following: >> >>Program received signal SIGUSR1. User defined signal 1 >>0x2818b1a3 in sigsuspend() from /usr/lib/libc.so.5. >> >> > >Unfortunately the bug is in a kernel module (the ?? lines >in your backtrace). Could you possibly compile a custom >kernel that has everything you use in it and then reproduce >this bug and get a trace? > > > >>Peter >> >> > > > -- Regards Peter As always the organisation disavows knowledge of this email To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message