dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460
Date: Tue, 14 Feb 2017 19:32:16 +0000	[thread overview]
Message-ID: <bug-99275-502-iLKfDqI8dg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99275-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2006 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99275

--- Comment #33 from Reimar Imhof <tuxuser@quantentunnel.de> ---
(In reply to Michel Dänzer from comment #27)
> (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.
> > 
> > With 
> > 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 that
> it behaves any differently from either of its parent commits. So git bisect
> should 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).

I forgot to mention:
I had a look at the first merge commits. I did _not_ do a "git bisect" but for
example a "git reset --hard 7af8a0f8088831428051976cb06cc1e450f8bab5" followed
by a "make rpm" to compile "Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux".
"e606d81d2d9596ab2b4fd0dc052eea0485b7e8c2
Merge branch 'ras-core-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip" was a good commit - no
problems at idle cpu as described in Comment #23.
That one was followed by "af79ad2b1f337a00aa150b993635b10bc68dc842
Merge branch 'sched-core-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip" which turned out to be
the first bad commit (glitches at 0 cpu load).
So all tested commits were pure merge commits.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3177 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-02-14 19:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 19:25 [Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460 bugzilla-daemon
2017-01-04 19:34 ` bugzilla-daemon
2017-01-04 21:17 ` bugzilla-daemon
2017-01-04 21:17 ` bugzilla-daemon
2017-01-04 21:18 ` bugzilla-daemon
2017-01-04 21:24 ` bugzilla-daemon
2017-01-04 21:35 ` bugzilla-daemon
2017-01-05  9:56 ` bugzilla-daemon
2017-01-05 18:09 ` bugzilla-daemon
2017-01-05 18:36 ` bugzilla-daemon
2017-01-16 20:55 ` bugzilla-daemon
2017-01-29 19:03 ` bugzilla-daemon
2017-01-29 19:04 ` bugzilla-daemon
2017-01-29 19:11 ` bugzilla-daemon
2017-01-29 19:13 ` bugzilla-daemon
2017-01-31  6:42 ` bugzilla-daemon
2017-02-01 21:08 ` bugzilla-daemon
2017-02-01 22:10 ` bugzilla-daemon
2017-02-03 20:05 ` bugzilla-daemon
2017-02-03 20:11 ` bugzilla-daemon
2017-02-03 20:46 ` bugzilla-daemon
2017-02-12 16:12 ` bugzilla-daemon
2017-02-12 16:17 ` bugzilla-daemon
2017-02-12 16:30 ` bugzilla-daemon
2017-02-12 19:21 ` bugzilla-daemon
2017-02-13  3:10 ` bugzilla-daemon
2017-02-13 18:55 ` bugzilla-daemon
2017-02-14  2:10 ` bugzilla-daemon
2017-02-14 11:55 ` bugzilla-daemon
2017-02-14 11:57 ` bugzilla-daemon
2017-02-14 12:02 ` bugzilla-daemon
2017-02-14 14:05 ` bugzilla-daemon
2017-02-14 15:29 ` bugzilla-daemon
2017-02-14 19:32 ` bugzilla-daemon [this message]
2017-02-22 21:25 ` bugzilla-daemon
2017-02-22 21:26 ` bugzilla-daemon
2018-03-24 11:20 ` bugzilla-daemon
2018-12-19 20:07 ` bugzilla-daemon
2019-11-19  8:12 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-99275-502-iLKfDqI8dg@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox