From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 85866] Desktop environment becomes unresponsive, but mouse can move after distro update Date: Fri, 07 Nov 2014 08:44:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1308917418==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2F9746EA10 for ; Fri, 7 Nov 2014 00:44:35 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1308917418== Content-Type: multipart/alternative; boundary="1415349875.6F6C4D31.28139"; charset="UTF-8" --1415349875.6F6C4D31.28139 Date: Fri, 7 Nov 2014 08:44:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D85866 --- Comment #7 from Michel D=C3=A4nzer --- (In reply to boombatower from comment #5) > Is there some reasonable instructions for performing a git bisect? I am > familiar with all sorts of development, but not a kernel developer. Is it > safe to assume this is in the driver and not Xorg? Yes, but it might be in the kernel or in Mesa. So if you can try the previo= us version of the kernel or Mesa again first, that would help identify which it is. Answering your question from IRC: Don't restrict git bisect to a subdirecto= ry of the kernel or Mesa tree, unless you're 100% sure the problem was caused = in there, or the bisection might give the wrong result. Also, only declare a commit as good once you're 100% (or as close to that as reasonably possible) sure that it's not affected by the problem, or again t= he bisection might give the wrong result. Take your time to enjoy the commits where the problem doesn't occur. :) --=20 You are receiving this mail because: You are the assignee for the bug. --1415349875.6F6C4D31.28139 Date: Fri, 7 Nov 2014 08:44:35 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comment= # 7 on bug 85866<= /a> from Michel D=C3=A4nzer 
(In reply to boombatower from comment #5)
> Is there some reasonable instructions for perfor=
ming a git bisect? I am
> familiar with all sorts of development, but not a kernel developer. Is=
 it
> safe to assume this is in the driver and not Xorg?

Yes, but it might be in the kernel or in Mesa. So if you can try the previo=
us
version of the kernel or Mesa again first, that would help identify which it
is.

Answering your question from IRC: Don't restrict git bisect to a subdirecto=
ry
of the kernel or Mesa tree, unless you're 100% sure the problem was caused =
in
there, or the bisection might give the wrong result.

Also, only declare a commit as good once you're 100% (or as close to that as
reasonably possible) sure that it's not affected by the problem, or again t=
he
bisection might give the wrong result. Take your time to enjoy the commits
where the problem doesn't occur. :)

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1415349875.6F6C4D31.28139-- --===============1308917418== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1308917418==--