From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97260] R9 290 low performance in Linux 4.7
Date: Tue, 09 Aug 2016 13:45:48 +0000 [thread overview]
Message-ID: <bug-97260-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1405 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97260
Bug ID: 97260
Summary: R9 290 low performance in Linux 4.7
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Keywords: regression
Severity: major
Priority: high
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: magolobel@yahoo.com.br
Starting with Linux Kernel 4.7, the Radeon R9 290 started showing very low
performance, about 20/30% of what is available up to kernel 4.6. As can be seen
in this article, the performance regression started even before the launch of
kernel 4.7 RC1, using Alex Deucher's drm-next-4.7 branch:
http://www.phoronix.com/scan.php?page=article&item=radeon-drm-next-47&num=1
Some time later it was speculated that the problem may be with DPM:
http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.7-R9-290-Regression
To replicate the bug, install Ubuntu 16.04 64bits and install kernel 4.7 from
here (preferably above rc5):
http://kernel.ubuntu.com/~kernel-ppa/mainline/
The performance regression will show right away. Rebooting the system and
choosing a kernel version up to 4.6 will fix the bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3027 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
next reply other threads:[~2016-08-09 13:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 13:45 bugzilla-daemon [this message]
2016-08-09 13:48 ` [Bug 97260] R9 290 low performance in Linux 4.7 bugzilla-daemon
2016-08-10 18:45 ` bugzilla-daemon
2016-08-10 19:17 ` bugzilla-daemon
2016-08-10 19:40 ` bugzilla-daemon
2016-08-10 19:43 ` bugzilla-daemon
2016-08-10 19:51 ` bugzilla-daemon
2016-08-10 20:25 ` bugzilla-daemon
2016-08-10 20:52 ` bugzilla-daemon
2016-08-10 21:00 ` bugzilla-daemon
2016-08-11 17:07 ` bugzilla-daemon
2016-08-11 19:35 ` bugzilla-daemon
2016-08-12 19:58 ` [Bug 97260] [bisected] " bugzilla-daemon
2016-08-12 19:58 ` bugzilla-daemon
2016-08-13 18:49 ` bugzilla-daemon
2016-08-15 17:57 ` bugzilla-daemon
2016-08-15 18:12 ` bugzilla-daemon
2016-08-15 20:02 ` bugzilla-daemon
2016-08-16 3:52 ` bugzilla-daemon
2016-08-16 6:15 ` bugzilla-daemon
2016-08-16 15:49 ` bugzilla-daemon
2016-08-17 8:05 ` bugzilla-daemon
2016-08-17 16:31 ` bugzilla-daemon
2016-08-18 1:02 ` bugzilla-daemon
2016-08-18 1:03 ` bugzilla-daemon
2016-08-19 6:22 ` 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-97260-502@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