From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110211] [regression] amdgpu Fury X Unplayable Slow Down on Dota 2
Date: Fri, 01 Jan 2016 11:14:56 +0000 [thread overview]
Message-ID: <bug-110211-2300-3Z39Sa8QRA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-110211-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=110211
Mike Lothian <mike@fireburn.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mike@fireburn.co.uk
--- Comment #2 from Mike Lothian <mike@fireburn.co.uk> ---
It's not a regression, you'll need to get a kernel from drm-next (with
amdgpu.powerplay=1 set) or a kernel from the powerplay branch in order to get
your card to clock to its maximum frequencies during gaming. Equally you could
wait for kernel 4.5-rc1 to be released
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-01 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 1:49 [Bug 110211] New: AMDGPU Fury X Unplayable Slow Down on Dota 2 bugzilla-daemon
2016-01-01 1:50 ` [Bug 110211] " bugzilla-daemon
2016-01-01 1:53 ` [Bug 110211] amdgpu " bugzilla-daemon
2016-01-01 1:58 ` [Bug 110211] [regression] " bugzilla-daemon
2016-01-01 2:06 ` bugzilla-daemon
2016-01-01 11:14 ` bugzilla-daemon [this message]
2016-01-01 14:05 ` bugzilla-daemon
2016-01-01 20:32 ` bugzilla-daemon
2016-01-01 20:33 ` [Bug 110211] [regression bisected] " bugzilla-daemon
2016-01-08 22:58 ` 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-110211-2300-3Z39Sa8QRA@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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