From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 62861] Maximum CPU voltage level never reached on AMD A8-5500 if radeon.dpm=1 is used
Date: Sat, 19 Oct 2013 13:13:52 +0000 [thread overview]
Message-ID: <bug-62861-12968-Bu8h26eP5J@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62861-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=62861
Kertesz Laszlo <laszlo.kertesz@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|Power Management |Drivers
Summary|Maximum CPU voltage level |Maximum CPU voltage level
|never reached on AMD |never reached on AMD
|A8-5500 |A8-5500 if radeon.dpm=1 is
| |used
Component|cpufreq |Video(DRI - non Intel)
--- Comment #4 from Kertesz Laszlo <laszlo.kertesz@gmail.com> ---
This issue is related to the radeon driver's dpm code.
If i dont append radeon.dpm=1 to the kernel boot options, i have 0.9-1.34v and
correct CPU speeds (including torbo boost).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-10-19 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 3:21 [Bug 62861] New: Maximum CPU voltage level never reached on AMD A8-5500 bugzilla-daemon
2013-10-12 3:46 ` [Bug 62861] " bugzilla-daemon
2013-10-13 4:06 ` bugzilla-daemon
2013-10-13 4:07 ` bugzilla-daemon
2013-10-19 13:13 ` bugzilla-daemon [this message]
2013-10-21 3:39 ` [Bug 62861] Maximum CPU voltage level never reached on AMD A8-5500 if radeon.dpm=1 is used bugzilla-daemon
2013-11-13 13:37 ` [Bug 62861] [BISECTED]Maximum " bugzilla-daemon
2013-11-20 7:12 ` 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-62861-12968-Bu8h26eP5J@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.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).