From owner-freebsd-current@FreeBSD.ORG Sat Jan 10 01:05:53 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 88D46106566C; Sat, 10 Jan 2009 01:05:53 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id E99C18FC1A; Sat, 10 Jan 2009 01:05:52 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so65252ugs.39 for ; Fri, 09 Jan 2009 17:05:51 -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:mime-version:content-type:content-transfer-encoding :content-disposition; bh=ZzA1Wz29aS3LAVQRKEa5MI+v4M9CzdAJPymEW2M9r5U=; b=tRs5z+NZAwjm/gTEK9IyO+IjqYFgW1PkhAXXiCVYHOfYxAWpkG5xIYxKFlF7CFiXti v7wb6PnSMKJZGIdKwkqakl6WSh2/r1BKaXMwnMBiVO5R6aYJSgUmDQjNpf81rOKb8Elf m9WCCEdkQ/GJBtIK6cEuwWNFt06xNRATiv+xA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type :content-transfer-encoding:content-disposition; b=a7jQoTw5wZVgHXw94y7U8BvchFlNX2UKnf/lcFf9hLsE6Q2ASLsD21g3gUmhxUzKY3 1TiHP4uLCvzzhWRFa4GolnO6fMcXvTaihJ1jC7luui0r2qr+wfj2vZkJne9nVF/c28lg ZfN1AbR4pCfCZ9Twjg3TCtVzuQaAzrFte+2dQ= Received: by 10.67.89.1 with SMTP id r1mr7343213ugl.82.1231549551213; Fri, 09 Jan 2009 17:05:51 -0800 (PST) Received: by 10.67.88.9 with HTTP; Fri, 9 Jan 2009 17:05:51 -0800 (PST) Message-ID: <7d6fde3d0901091705v6eb4c7bfxe23708f8651e2125@mail.gmail.com> Date: Fri, 9 Jan 2009 17:05:51 -0800 From: "Garrett Cooper" To: "Doug Barton" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: FreeBSD Current Subject: X becomes unresponsive with nvidia and hardlocks with gdb (was 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: Sat, 10 Jan 2009 01:05:54 -0000 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