From owner-freebsd-x11@FreeBSD.ORG Mon Jan 12 02:53:10 2009 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A72B1065670; Mon, 12 Jan 2009 02:53:10 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 743008FC12; Mon, 12 Jan 2009 02:53:09 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by bwz13 with SMTP id 13so5489963bwz.19 for ; Sun, 11 Jan 2009 18:53:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=vuTc/tDkBVbbEee7mcuJHaFLPLil3dBu03EZbd+EkEI=; b=vSDOVupfynAu5JsH4mHoMzViyQcLh52PRXsbmWzKufl+goyJnngmL3y6KmgSVgVtIP HXhV5r0gtgrTZSSF4ix9UWyvbhVbSUrzPAtR8xTZc6lz3dwLzGRbbQT+TMnKv7GfvFF1 PUE2k17K34UACMtP43Gwfq2ztUa7Uq8UIogko= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=PHoqcy5+ln7YQVUMXxXIbIuZRfTXwdO+8vm8r6GXKA7BCUz0FMDpMDqGWIRKm7rteH fiNMJzKX2E/hyCzN3lkhe2wZCgdb4RZNGptTv02ID3RDJjuWukLWzeJBZBo1Ck0ialLp TEpmYP7TktP+nekDIAHiIwPoD95ZWp5h9sNXg= Received: by 10.180.203.3 with SMTP id a3mr10786935bkg.146.1231728788322; Sun, 11 Jan 2009 18:53:08 -0800 (PST) Received: by 10.181.26.3 with HTTP; Sun, 11 Jan 2009 18:53:08 -0800 (PST) Message-ID: <7d6fde3d0901111853k40f26893j722d95d3556c820@mail.gmail.com> Date: Sun, 11 Jan 2009 18:53:08 -0800 From: "Garrett Cooper" To: "Doug Barton" In-Reply-To: <7d6fde3d0901091705v6eb4c7bfxe23708f8651e2125@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7d6fde3d0901091705v6eb4c7bfxe23708f8651e2125@mail.gmail.com> Cc: freebsd-x11 , FreeBSD Current Subject: Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 02:53:10 -0000 On Fri, Jan 9, 2009 at 5:05 PM, Garrett Cooper wrote: > On Fri, Jan 9, 2009 at 2:05 PM, Garrett Cooper wrote: >> On Fri, Jan 9, 2009 at 1:40 PM, Doug Barton wrote: >>> Garrett Cooper wrote: >>>> Thanks for the tips Doug -- I'll give them a shot of course... >>> >>> Glad I could help. The one thing I forgot to mention is to try the >>> nvidia-settings app if you have not already done so. There are various >>> things there that you can tweak that might yield better results. >>> >>> Doug >> >> I did in fact set everything up via nvidia-settings. I'm running >> some stress tests right now to see whether or not I can simulate the >> issue -- it doesn't appear to be as straightforward as I thought.. >> -Garrett >> > > I believe my actual problem with panicking is related to gdb, not X11. > So the actual problem is two-fold: > > - X11 livelocks, where I can login via ssh and kill . > - When I use gdb -p, it prints out the same message reported here: > . The only > thing is that if I press `y' on the first go-around, the machine > hardlocks on the first try with hitting `y'. If I hit `n' so gdb > coredumps, I can either go on my merry way, or go back to the > confirmation dialog. If I hit it again, it doesn't hardlock. It does > hardlock though, and for whatever reason my PC speaker beeps, and I > have to warm boot it. I haven't been able to get a kernel dump though, > so something else mysteriously is going on that I can't track. > > So, just to simplify: > > first_try := True > > while gdb is running: > if prompt_for_coredump() and first_try is True: > panic() > first_try := False > > Thanks, > -Garrett Ok, I've been doing some more poking around this weekend, and here's what I discovered: - I've rebuilt my xorg-server a few times and it's still claiming that it was built with 7.1-RC2 -_-... - I can get the Xorg server to go full tilt by just compiling something, like buildworld, via an xterm. - I can't attach truss to Xorg, or the Xorg will livelock. Now, trying out the nv driver: - It constantly uses up ~20% CPU on one of my four cores. When I compile something it chews up ~50% CPU. - I can attach truss to Xorg, but it drags the CPU up to ~100%. Xorg was spending a LOT of time pinging socket data around, which makes me think that what the nvidia driver is doing is actually unrooting a performance issue with the IPC mechanism in Xorg, as nv suffers from the same thing, just on a less grand scale; mind you, I can get both of my screens up and running under nvidia at different resolutions -- 1920x1200 and 1680 x 1050 -- but under nv I only get 2 displays setup at 1680 x 1050. - Detaching truss causes the livelock condition (again). Rebuilding xorg-server has proven to help so far. I did delete-old-files, and it appears that xorg-server may have been picking up some old libraries still. Let's see if this sticks or not... Cheers, -Garrett