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 103175] R9285 Unreal tournament perf regression with agd5f 4.15-wip kernels possibly CPU related
Date: Tue, 10 Oct 2017 09:01:27 +0000	[thread overview]
Message-ID: <bug-103175-502-EoBo4WjI3Z@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103175-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Andy Furniss <adf.lists@gmail.com> ---
I had that fix and a couple of others on the first 4.15-wip I tried. They are
in now AFAICT. I see Alex updated again since yesterday so I'll try that one
later.

I did notice but forgot to highlight the GPU difference.
Given all the powerplay changes in 4.15-wip I do wonder if all is well but I
would have expected Unigine/Xonotic to show it if something was wrong there.

One thing different about UT is it asks for more vram than I have, maybe that
makes it stand out from other tests.

After posting this I did wonder whether the CPU difference is just because the
fps is low and not the cause.

4.15-wip doesn't work for me going away from head (will throw  some vmfaults
and then lock soon after startx) so bisecting is not an easy option.

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

[-- Attachment #1.2: Type: text/html, Size: 1817 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-10-10  9:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 17:31 [Bug 103175] R9285 Unreal tournament perf regression with agd5f 4.15-wip kernels possibly CPU related bugzilla-daemon
2017-10-09 17:33 ` bugzilla-daemon
2017-10-09 17:35 ` bugzilla-daemon
2017-10-10  8:27 ` bugzilla-daemon
2017-10-10  8:29 ` bugzilla-daemon
2017-10-10  9:01 ` bugzilla-daemon [this message]
2017-10-11  9:59 ` bugzilla-daemon
2017-11-15 21:48 ` bugzilla-daemon
2017-11-16 15:35 ` bugzilla-daemon
2017-11-22  0:44 ` bugzilla-daemon
2017-11-22 11:42 ` 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-103175-502-EoBo4WjI3Z@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