From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@bugzilla.kernel.org Subject: [Bug 33912] [RV515] Kernel .35 onwards, Random X freezes while scrolling Date: Fri, 10 Jun 2011 15:10:40 GMT Message-ID: <201106101510.p5AFAeaZ006190@demeter1.kernel.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from demeter1.kernel.org (demeter1.kernel.org [140.211.167.39]) by gabe.freedesktop.org (Postfix) with ESMTP id ABAD59E796 for ; Fri, 10 Jun 2011 08:10:43 -0700 (PDT) Received: from demeter1.kernel.org (localhost.localdomain [127.0.0.1]) by demeter1.kernel.org (8.14.4/8.14.4) with ESMTP id p5AFAfPA006209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Jun 2011 15:10:43 GMT In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org https://bugzilla.kernel.org/show_bug.cgi?id=33912 --- Comment #11 from Alex Deucher 2011-06-10 15:10:39 --- (In reply to comment #10) > (In reply to comment #9) > > Can you bisect? > > I have never bisected a kernel, but I can try. Just have a few doubts. > > 1 * Can I do with the Ubuntu kernel as per Ubuntu instructions[0] as: > $ git bisect start Ubuntu-2.6.35-1.1 Ubuntu-2.6.34-5.14 > > Which seems a saner incremental interval of Jun5 -> Jun 4. That should be fine. The closest two kernels that where which have and don't have the problem are your best bet. > 2 * Are there any pointers to narrow down the kernel commit from the backtraces > I have posted? > Or is just looking for "drivers/gpu/drm/radeon/" the closest? You can narrow the bisection to just radeon, but if the problem is something non-radeon you'll get inconclusive results. > > 3 * Is there any specific command I need to run if I hit the bug? > Or is gdb of X sufficient? > Do I need to set any variables to get better logs of the freeze? It's really hard to narrow down what causes the GPU to hang. It could be a bug in the kernel, it could also be a certain combination of command buffers or userspace acceleration drivers that happen to make the GPU angry. Just getting the commit id should be enough. You might also try a newer ddx and/or mesa 3D driver to see if that helps. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.