From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109101] New: [A10-7800] CPU is capped to 3GHz if BAPM is enabled
Date: Wed, 09 Dec 2015 01:05:45 +0000 [thread overview]
Message-ID: <bug-109101-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=109101
Bug ID: 109101
Summary: [A10-7800] CPU is capped to 3GHz if BAPM is enabled
Product: Drivers
Version: 2.5
Kernel Version: 4.2.6
Hardware: x86-64
OS: Linux
Tree: Fedora
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: immarcescibilis@outlook.com
Regression: No
I have an A10-7800 APU with a 3.5GHz clock (3.9/3.8/3.6 turbo) on an MSI
A88XM-E45 board that doesn't seem to suffer from the lack of BAPM, since it was
disabled by default and I had to enable it manually, after doing some research
on how to enable TurboCore on Linux. The fact of the matter is not only that it
doesn't work at all, but that it caps the CPU clock to 3GHz even on full load.
If I disable BAPM, the clocks raise normally to 3.5GHz. In my tests, I've
noticed a couple of things:
- Cool'n'Quiet is irrelevant. BAPM throttles the CPU clock whether Cool'n'Quiet
is disabled or enabled;
- With BAPM enabled, both CPU and GPU temperatures rise together when on full
load, even if there's no GPU usage;
- The turbo frequencies are never reached.
I made all measurements with turbostat while running either POV-Ray or stress
--cpu.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-12-09 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 1:05 bugzilla-daemon [this message]
2016-02-08 16:44 ` [Bug 109101] [A10-7800] CPU is capped to 3GHz if BAPM is enabled 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-109101-2300@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).