From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 23:00:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29F6C1065694 for ; Thu, 8 Jan 2009 23:00:10 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 4C2E68FC18 for ; Thu, 8 Jan 2009 23:00:02 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1LL3r7-0004pm-Qe>; Fri, 09 Jan 2009 00:00:01 +0100 Received: from e178036186.adsl.alicedsl.de ([85.178.36.186] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1LL3r7-0004cT-N7>; Fri, 09 Jan 2009 00:00:01 +0100 Message-ID: <4966859E.7080301@mail.zedat.fu-berlin.de> Date: Fri, 09 Jan 2009 00:00:46 +0100 From: "O. Hartmann" User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Garrett Cooper References: <7d6fde3d0901072349i50d04d2ch34f308388c9fd414@mail.gmail.com> <20090108083645.GA56613@freebsd.org> <1A86A687-DA2D-4866-8825-8BBF021F6937@gmail.com> In-Reply-To: <1A86A687-DA2D-4866-8825-8BBF021F6937@gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.36.186 X-Mailman-Approved-At: Thu, 08 Jan 2009 23:08:22 +0000 Cc: Roman Divacky , FreeBSD Current Subject: Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics 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: Thu, 08 Jan 2009 23:00:11 -0000 Garrett Cooper wrote: > On Jan 8, 2009, at 12:36 AM, Roman Divacky wrote: > >> On Wed, Jan 07, 2009 at 11:49:26PM -0800, Garrett Cooper wrote: >>> Hello folks, >>> As many probably know, I recently installed FreeBSD 8-CURRENT on >>> my desktop. >>> One of the things I'm noting is that when I use dual displays with >>> the nvidia driver, and xscreensaver kicks in and keeps going for a >>> period of time, the machine's X.org console eats up a core, and when I >>> try and do anything like gdb Xorg, the system hangs, attempts to panic >>> (I assume that's the case because I hear it beep and attempt to >>> restart), then I have to give it a warm boot. truss(1)'ing Xorg showed >>> that there were a lot of SIGALARM's being fired and masked. >>> This is incredibly reminiscent of the days when I used to run >>> Linux and >>> I forgot to configure my dump device (doh), but this problem >>> appears >>> to be easily reproducible with my environment. I'm fixing that issue >>> right now, so I should have a working crashdump soon... >>> Just wondering if anyone else has seen this issue, or if it's >>> just me >>> once again. >>> Thanks, >> >> the nvidia driver keeps my 8-current crashing/deadlocking when >> playing video >> quite often (once a week?). I have no idea what it causes. >> >> the code of the driver seems to be done in 5.x times. I believe it needs >> some rehashing as it might not get the semantics of "things" in 8.x >> right > > > Hey Roman! > Yeah, I'm fine with it being slow, for a little while, as long as > it's functional... I do realize that nvidia is still giant locked > (ew..), so it might be some nasty resource contention. > Are you using Linux emulation support with the driver? > Cheers, > -Garrett > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" I have and I had the same in FreeBSD 7.0/7.1 and now with 8.0-CUR with both a NV8600GTS and an older NV6800GT. A very old NV6600 never showed up these lockings when I used that PCIe-Card with FreeBSD 7.0/7.1, but I'm not sure. The locks came spontanous, sometimes after heavy usage of 'mplayer', but sometimes instantanously after the destop showed up. On those boxes, there is no Linux emulation and no Linux BLOB (useless, due to 64 Bit). I swapped the 'nv' driver on all FreeBSD boxes with 'vesa', because there is another issue with sprites/graphics buffers many times reported using FireFox. When the display got locked, sometimes I had the chance opening a ssh session killing Xorg/xdm and restarting working, but by the end, that was when changing towards 8.0-CUR, this 'trick' didn't work anymore. On FBSD 7, Xorg was eating up 100% CPU time.