From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions Date: Sat, 19 Dec 2015 16:33:20 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1364478598==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B527E6E03B for ; Sat, 19 Dec 2015 08:33:20 -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 --===============1364478598== Content-Type: multipart/alternative; boundary="1450542800.fF673E0.16393"; charset="UTF-8" --1450542800.fF673E0.16393 Date: Sat, 19 Dec 2015 16:33:20 +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=3D92858 --- Comment #16 from Darren D. --- (In reply to Michel D=C3=A4nzer from comment #15) > (In reply to Michel D=C3=A4nzer from comment #14) > > ... I think you'll need to restart the bisection process with > > 744b058827b3db9a4f6027522dd9c73a208c2d31 as the initial good commit [..= .] >=20 > Actually, you can start with 91d9f9856f91c82ac6289a0fff65dd12cfa07e34 as = the > initial good commit. I can restart it yet again, and at least this time it'll be a narrower rang= e of commits. And this is the sequence of commands I should use to do that, correct? git bisect start git bisect good 91d9f9856f91c82ac6289a0fff65dd12cfa07e34 git bisect bad 692a59e696afe1a4e777d0e4359325336ab0ad89 And if I start running into unbootable kernels again, I should start a new bisect with a different copy of the source tree and identify at which commit the compiled kernel started failing to boot, shouldn't I? --=20 You are receiving this mail because: You are the assignee for the bug. --1450542800.fF673E0.16393 Date: Sat, 19 Dec 2015 16:33:20 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 16 on bug 92858<= /a> from Darren D. 
(In reply to Michel D=C3=A4nzer from comment #15)
> (In reply to Michel D=C3=A4nzer from comment #14)
> > ... I think you'll need to restart the bisection process with
> > 744b058827b3db9a4f6027522dd9c73a208c2d31 as the initial good comm=
it [...]
>=20
> Actually, you can start with 91d9f9856f91c82ac6289a0fff65dd12cfa07e34 =
as the
> initial good commit.

I can restart it yet again, and at least this time it'll be a narrower rang=
e of
commits.

And this is the sequence of commands I should use to do that, correct?

git bisect start

git bisect good 91d9f9856f91c82ac6289a0fff65dd12cfa07e34

git bisect bad 692a59e696afe1a4e777d0e4359325336ab0ad89

And if I start running into unbootable kernels again, I should start a new
bisect with a different copy of the source tree and identify at which commit
the compiled kernel started failing to boot, shouldn't I?

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