From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81021] AMD CPUs w/ Integrated Graphics (APUs) And Turbo Core Only Boost If "fglrx" Module Is Loaded
Date: Tue, 29 Jul 2014 23:35:49 +0000 [thread overview]
Message-ID: <bug-81021-2300-UOUjx5lwz9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-81021-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=81021
Kertesz Laszlo <laszlo.kertesz@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |laszlo.kertesz@gmail.com
--- Comment #3 from Kertesz Laszlo <laszlo.kertesz@gmail.com> ---
This issue isnt new, i filed a bug about it ages ago ( #62861 ). As Alex said,
turbo core can be enabled by setting bapm to true.
Now this is enabled on MSI boards (seems to me all had A78 chipsets?) only by
default because they had reboots right after boot if it was off.
Im curious how they fare with enabled bapm.
Problem is setting bapm on, at least on my A8-6500/GA-F2A88X-D3H and my former
A8-5500/GA-F2A85X-D3H hardware causes random reboots or system hangs with no
outputs in the system logs.
The setting indeed enables turbo core.
Also, a simpler way of seeing the actual working frequency is loading the msr
module:
modprobe msr
Then running:
cpufreq-aperf
or
cpufreq-aperf -o
for a single poll.
both commands with root rights. This will show the actual frequency in Hz
(which sometimes is between the nominal p-states, or maybe the polling does
averages).
Additionally, even if fglrx eables turbo core boost, sometimes something weird
happens and even the nominal speed is reported as maximum, in effect you can
have even as low as 1.8 GHz (3.2GHz CPU) after an initial turbo boosted speed
which lasts a few seconds. This happened to me sometimes (almost 50% of times)
when i was compiling with 4 threads on my older A8-5500. I suppose its some
internal downclocking mechanism kicking in at the wrong time because the
reported temperatures were ~55C (default cooler).
In contrast this never happened with radeon and if one thread was used it could
have 4 GHz for hours (runaway flash in browser for example). 4 threads
(compile) usually settled all cores at a stable ~3.7-3.8 GHz (temps up to 60C,
default cooler). These are values on the A8-6500 (3.5GHz nominal/4.1 GHz turbo
speed from which never exceeded 4.0 as long as i monitored it).
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-07-29 23:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-81021-2300@https.bugzilla.kernel.org/>
2014-07-29 15:18 ` [Bug 81021] AMD CPUs w/ Integrated Graphics (APUs) And Turbo Core Only Boost If "fglrx" Module Is Loaded bugzilla-daemon
2014-07-29 15:18 ` bugzilla-daemon
2014-07-29 16:03 ` bugzilla-daemon
2014-07-29 23:35 ` bugzilla-daemon [this message]
2014-07-30 12:18 ` bugzilla-daemon
2014-07-30 12:32 ` bugzilla-daemon
2014-07-30 13:24 ` bugzilla-daemon
2014-08-03 17:34 ` bugzilla-daemon
2014-08-04 14:53 ` bugzilla-daemon
2014-08-07 9:34 ` bugzilla-daemon
2014-08-07 9:43 ` bugzilla-daemon
2014-08-07 13:21 ` bugzilla-daemon
2014-08-07 13:31 ` bugzilla-daemon
2014-08-07 15:17 ` bugzilla-daemon
2014-08-07 15:24 ` 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-81021-2300-UOUjx5lwz9@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).