From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60523] Radeon DPM not working with 2 monitors attached to Radeon HD5770 (Juniper)
Date: Wed, 11 Jun 2014 10:26:50 +0000 [thread overview]
Message-ID: <bug-60523-2300-B5s4U3H8M5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60523-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60523
Mathias Tillman <master.homer@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |master.homer@gmail.com
--- Comment #54 from Mathias Tillman <master.homer@gmail.com> ---
Just thought I'd drop by and say that I have the same problem on my XFX Radeon
HD 6870 using kernel 3.15.0-rc3+ (compiled from the latest agd5f repo) when I
have two monitors attached. Trying to echo to power_dpm_force_performance_level
results in an "Invalid argument" like others have mentioned as well.
What's interesting here is that I tried overriding the sclk and mclk level
values in the code (in btc_dpm.c, btc_apply_state_adjust_rules), I changed the
sclk and mclk for the medium and high levels from 77500, 105000 to 25000, 42000
and 90000, 105000 to 40000, 50000 respectively. And now it doesn't get stuck in
the highest level anymore and I can successfully override the performance level
using power_dpm_force_performance_level.
I'm not really sure what is causing all this, but I do know that
btc_dpm_vblank_too_short return false on stock values, so it's not that at
least.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-06-11 10:26 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 16:57 [Bug 60523] New: Lockup with radeon DPM on Radeon HD5770 (Juniper) bugzilla-daemon
2013-07-09 18:01 ` [Bug 60523] " bugzilla-daemon
2013-07-09 18:27 ` bugzilla-daemon
2013-07-09 18:42 ` bugzilla-daemon
2013-07-09 19:46 ` bugzilla-daemon
2013-07-30 17:37 ` bugzilla-daemon
2013-07-30 17:45 ` bugzilla-daemon
2013-07-30 17:49 ` bugzilla-daemon
2013-07-30 17:57 ` bugzilla-daemon
2013-07-30 21:50 ` bugzilla-daemon
2013-07-30 21:51 ` bugzilla-daemon
2013-07-30 21:59 ` bugzilla-daemon
2013-08-01 22:54 ` bugzilla-daemon
2013-08-01 23:16 ` bugzilla-daemon
2013-08-02 16:31 ` bugzilla-daemon
2013-08-04 18:54 ` bugzilla-daemon
2013-08-04 23:25 ` bugzilla-daemon
2013-08-15 4:00 ` [Bug 60523] Radeon DPM not working with 2 monitors attached to " bugzilla-daemon
2013-08-15 12:32 ` bugzilla-daemon
2013-08-15 15:53 ` bugzilla-daemon
2013-08-15 18:54 ` bugzilla-daemon
2013-08-15 20:09 ` bugzilla-daemon
2013-08-15 20:52 ` bugzilla-daemon
2013-08-15 20:56 ` bugzilla-daemon
2013-08-15 21:08 ` bugzilla-daemon
2013-08-15 21:18 ` bugzilla-daemon
2013-08-15 21:27 ` bugzilla-daemon
2013-08-15 21:40 ` bugzilla-daemon
2013-08-15 21:43 ` bugzilla-daemon
2013-08-15 21:46 ` bugzilla-daemon
2013-08-15 21:55 ` bugzilla-daemon
2013-08-15 22:09 ` bugzilla-daemon
2013-08-15 22:16 ` bugzilla-daemon
2013-08-15 22:41 ` bugzilla-daemon
2013-08-19 2:04 ` bugzilla-daemon
2013-08-19 2:30 ` bugzilla-daemon
2013-08-19 18:46 ` bugzilla-daemon
2013-08-19 18:57 ` bugzilla-daemon
2013-08-20 14:40 ` bugzilla-daemon
2013-08-20 16:15 ` bugzilla-daemon
2013-08-20 16:50 ` bugzilla-daemon
2013-08-20 21:18 ` bugzilla-daemon
2013-08-20 21:24 ` bugzilla-daemon
2013-08-20 21:37 ` bugzilla-daemon
2013-09-05 22:32 ` bugzilla-daemon
2013-11-02 7:57 ` bugzilla-daemon
2013-11-04 14:05 ` bugzilla-daemon
2014-02-01 20:36 ` bugzilla-daemon
2014-02-01 20:38 ` bugzilla-daemon
2014-02-01 20:39 ` bugzilla-daemon
2014-03-06 21:04 ` bugzilla-daemon
2014-03-07 6:35 ` bugzilla-daemon
2014-03-07 8:02 ` bugzilla-daemon
2014-05-12 20:50 ` bugzilla-daemon
2014-05-13 23:09 ` bugzilla-daemon
2014-06-11 10:26 ` bugzilla-daemon [this message]
2014-07-01 22:51 ` bugzilla-daemon
2014-07-02 0:49 ` bugzilla-daemon
2014-07-02 9:39 ` bugzilla-daemon
2014-07-03 13:56 ` bugzilla-daemon
2014-07-03 15:15 ` bugzilla-daemon
2014-07-03 17:47 ` bugzilla-daemon
2014-07-03 23:20 ` bugzilla-daemon
2014-12-04 14:01 ` bugzilla-daemon
2014-12-04 18:49 ` bugzilla-daemon
2014-12-04 19:01 ` bugzilla-daemon
2014-12-04 19:06 ` bugzilla-daemon
2014-12-04 19:14 ` bugzilla-daemon
2015-02-13 12:28 ` bugzilla-daemon
2015-02-14 5:34 ` bugzilla-daemon
2015-05-24 9:43 ` bugzilla-daemon
2015-05-28 9:59 ` bugzilla-daemon
2015-05-30 3:40 ` bugzilla-daemon
2015-10-30 12:44 ` bugzilla-daemon
2016-01-24 15:52 ` bugzilla-daemon
2016-03-05 4:41 ` bugzilla-daemon
2016-03-06 0:49 ` bugzilla-daemon
2016-03-06 0:50 ` bugzilla-daemon
2016-03-13 3:51 ` 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-60523-2300-B5s4U3H8M5@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;
as well as URLs for NNTP newsgroup(s).