From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82055] New: [HAWAII] Running some programs, when HW acceleration is on, causes X to spike in CPU usage → unresponsive desktop
Date: Sat, 02 Aug 2014 15:35:47 +0000 [thread overview]
Message-ID: <bug-82055-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2120 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=82055
Priority: medium
Bug ID: 82055
Assignee: dri-devel@lists.freedesktop.org
Summary: [HAWAII] Running some programs, when HW acceleration
is on, causes X to spike in CPU usage → unresponsive
desktop
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: kai@dev.carbon-project.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
When running certain programs (eg. MediathekView) or watching recorded
broadcasts on Twitch, X starts going up in CPU usage and the desktop becomes
unresponsive, until you kill the stream or the program has finished its draw
operations (can take several seconds). Interestingly enough, YouTube videos are
not affected. In both cases I had HW video acceleration on (through settings in
/etc/adobe/mms.conf), without HW acceleration the plugin is just consuming
ridiculous amounts of CPU cycles.
The problem with Twitch is independent off chosen video quality.
My desktop environment is KDE 4.13.3 with desktop effects enabled (compositing
type=OpenGL 3.1, render target=native), disabling them has no effect on this
issue.
I haven't seen these issues with my previous HD7850 (also using Glamor),
therefore I think this is separate to bug 68524.
My stack is (base: Debian Testing):
GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1)
Linux: Git:~agdf5/linux:drm-next-3.17-rebased-on-fixes:fa053e7263 (calls itself
3.16-rc6) + attachment 93015 [details] [review]
libdrm: Git:master/libdrm-2.4.56
LLVM: SVN:trunk/r214546 (3.6 snapshot)
libclc: Git:master/5b48f170c8
Mesa: Git:master/e41cc45361
DDX: Git:master/4b5060f357 + Patch from
http://lists.x.org/archives/xorg-driver-ati/2014-July/026517.html
X: 2:1.16.0-2 (1.16.0)
Let me know, if you need further information.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4046 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-08-02 15:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 15:35 bugzilla-daemon [this message]
2014-08-04 3:45 ` [Bug 82055] [HAWAII] Running some programs, when HW acceleration is on, causes X to spike in CPU usage → unresponsive desktop bugzilla-daemon
2014-08-04 6:04 ` bugzilla-daemon
2014-08-04 7:08 ` bugzilla-daemon
2014-08-04 8:55 ` bugzilla-daemon
2014-08-04 8:59 ` bugzilla-daemon
2014-08-04 9:50 ` bugzilla-daemon
2014-08-04 10:35 ` bugzilla-daemon
2014-08-04 14:27 ` bugzilla-daemon
2014-08-04 14:27 ` bugzilla-daemon
2014-08-04 14:27 ` bugzilla-daemon
2014-08-04 14:30 ` bugzilla-daemon
2014-08-04 14:58 ` bugzilla-daemon
2014-08-04 15:03 ` bugzilla-daemon
2014-08-05 7:00 ` bugzilla-daemon
2014-11-25 21:26 ` 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-82055-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.