From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 45641] Screen goes black randomly Date: Tue, 19 Mar 2013 14:01:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1057900621==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A9DCEE6510 for ; Tue, 19 Mar 2013 07:01:23 -0700 (PDT) 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 --===============1057900621== Content-Type: multipart/alternative; boundary="1363701683.53Ea81.8956"; charset="us-ascii" --1363701683.53Ea81.8956 Date: Tue, 19 Mar 2013 14:01:23 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=45641 --- Comment #11 from Alex Deucher --- (In reply to comment #10) > > For systems where this is a regression, can you bisect? > > I don't understand. Could you explain this question please (if it was to me)? If it worked with an older kernel, you can use git to bisect between working kernel and the the broken one. Bisecting allows you to pinpoint the change that caused the problem. There are a number of good tutorials on using git to bisect a problem. -- You are receiving this mail because: You are the assignee for the bug. --1363701683.53Ea81.8956 Date: Tue, 19 Mar 2013 14:01:23 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 11 on bug 45641 from 
(In reply to comment #10)
> > For systems where this is a regression, can you bisect?
> 
> I don't understand. Could you explain this question please (if it was to me)?

If it worked with an older kernel, you can use git to bisect between working
kernel and the the broken one.  Bisecting allows you to pinpoint the change
that caused the problem.  There are a number of good tutorials on using git to
bisect a problem.

You are receiving this mail because:
  • You are the assignee for the bug.
--1363701683.53Ea81.8956-- --===============1057900621== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1057900621==--