From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460 Date: Tue, 14 Feb 2017 02:10:28 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1546166980==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 4A2B86E5D4 for ; Tue, 14 Feb 2017 02:10:28 +0000 (UTC) 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 --===============1546166980== Content-Type: multipart/alternative; boundary="14870382280.aD6FF153.9874"; charset="UTF-8" --14870382280.aD6FF153.9874 Date: Tue, 14 Feb 2017 02:10:28 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D99275 --- Comment #27 from Michel D=C3=A4nzer --- (In reply to Reimar Imhof from comment #26) > Together with comment #24 there is a render bug in kernel 4.8 that shows = up > at 100% cpu load. > With kernel 4.9 this same bug shows up at 0% / idle cpu load. >=20 > With=20 > af79ad2b1f337a00aa150b993635b10bc68dc842 > Merge branch 'sched-core-for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip > it changed from "bug shows at 100% load" to "bug shows at 0% load". And t= he > change is something about the scheduler. > To me this seems likely. Not really. That commit is a pure merge commit, which makes it unlikely tha= t it behaves any differently from either of its parent commits. So git bisect sh= ould have identified one of its ancestor commits instead. The fact that it identified a pure merge commit indicates that the result is incorrect, most likely because at least one commit along the way was incorrectly classified= as good (or bad). --=20 You are receiving this mail because: You are the assignee for the bug.= --14870382280.aD6FF153.9874 Date: Tue, 14 Feb 2017 02:10:28 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 27 on bug 99275<= /a> from Michel D=C3=A4nzer 
(In reply to Reimar Imhof from comment #26)
> Together with comment #24 there is a render bug in kernel 4.8 that shows up
> at 100% cpu load.
> With kernel 4.9 this same bug shows up at 0% / idle cpu load.
>=20
> With=20
> af79ad2b1f337a00aa150b993635b10bc68dc842
> Merge branch 'sched-core-for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> it changed from "bug shows at 100% load" to "bug shows =
at 0% load". And the
> change is something about the scheduler.
> To me this seems likely.

Not really. That commit is a pure merge commit, which makes it unlikely tha=
t it
behaves any differently from either of its parent commits. So git bisect sh=
ould
have identified one of its ancestor commits instead. The fact that it
identified a pure merge commit indicates that the result is incorrect, most
likely because at least one commit along the way was incorrectly classified=
 as
good (or bad).

You are receiving this mail because:
  • You are the assignee for the bug.
= --14870382280.aD6FF153.9874-- --===============1546166980== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1546166980==--