From owner-freebsd-questions@FreeBSD.ORG Thu Jul 7 09:40:29 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CEDB16A41C for ; Thu, 7 Jul 2005 09:40:29 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28EE743D48 for ; Thu, 7 Jul 2005 09:40:28 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out4.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Thu, 7 Jul 2005 10:41:10 +0100 Message-ID: <42CCF88B.60504@dial.pipex.com> Date: Thu, 07 Jul 2005 10:40:27 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: Andreas Kohn References: <1120686579.2782.4.camel@klamath.syndrom23.de> In-Reply-To: <1120686579.2782.4.camel@klamath.syndrom23.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Jul 2005 09:41:10.0943 (UTC) FILETIME=[021562F0:01C582D8] Cc: mikef@ack.Berkeley.EDU, freebsd-questions@freebsd.org Subject: Re: FreeBSD locks up when X-windows running (LONG) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2005 09:40:29 -0000 Andreas Kohn wrote: >Hi, > >say, do you see any messages like > >NVRM: Xid: 13, 0000 02005600 00000056 00000c28 006500ac 00000080 > >(Numbers may vary, I think) >in your kernel messages after such a lock-up happened? > > AFAIK this is not a FreeBSD-specific problem. I think this URL is right but the site isn't responding at the moment. I don't know if there is a solution there or not. There were some interesting comments about running glxgears before running a game making things better, if that's the kind of thing you are doing (gaming, that is), but I never got to the end of the thread. Most people reported the problem on much newer cards but the Xid is the classic symptom. http://www.nvnews.net/vbulletin/showthread.php?t=49117 You could always try the nv drivers. My Ge2 worked fine on them for years, while my 6600 suffered corruption at least once a day. --Alex