From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82055] [HAWAII] Running some programs, when HW acceleration is on, causes X to spike in CPU usage → unresponsive desktop
Date: Mon, 04 Aug 2014 06:04:27 +0000 [thread overview]
Message-ID: <bug-82055-502-R3gJc2SBAe@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82055-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 950 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=82055
--- Comment #2 from Kai <kai@dev.carbon-project.org> ---
(In reply to comment #1)
> Please attach the Xorg.0.log and the output of dmesg and glxinfo.
Will post those later, when I'm back at that system.
> Is this with DPM successfully changing clocks?
As written in bug 74250, comment #8 reclocking doesn't seem to work for me.
Whatever I've been doing, the output of cat
/sys/kernel/debug/dri/0/radeon_pm_info /sys/kernel/debug/dri/64/radeon_pm_info
stays:
> power level avg sclk: 30000 mclk: 15000
> power level avg sclk: 30000 mclk: 15000
(observed through a SSH connection, in order to keep the 3D applications
running fullscreen). I can check the clocks with e.g. MediathekView too, but it
would be very weird if the GPU would reclock for "simple" applications and not
for the 3D applications, wouldn't it?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2249 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 prev parent reply other threads:[~2014-08-04 6:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 15:35 [Bug 82055] New: [HAWAII] Running some programs, when HW acceleration is on, causes X to spike in CPU usage → unresponsive desktop bugzilla-daemon
2014-08-04 3:45 ` [Bug 82055] " bugzilla-daemon
2014-08-04 6:04 ` bugzilla-daemon [this message]
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-R3gJc2SBAe@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;
as well as URLs for NNTP newsgroup(s).