From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 101241] New: cpufreq ondemand not work in my system
Date: Thu, 09 Jul 2015 03:26:14 +0000 [thread overview]
Message-ID: <bug-101241-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=101241
Bug ID: 101241
Summary: cpufreq ondemand not work in my system
Product: Power Management
Version: 2.5
Kernel Version: 2.6.32
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: jakepain@gmail.com
Regression: No
I want to use cpufreq "ondemand" policy to change the CPU frequency dynamiclly.
But when I insmod the powernow-k8 driver, it detected below data
Jul 9 11:11:43 localhost kernel: powernow-k8: Found 1 AMD GX-416RA SOC
(4 cpu cores) (version 2.20.00)
Jul 9 11:11:43 localhost kernel: powernow-k8: 0 : pstate 0 (1600 MHz)
Jul 9 11:11:43 localhost kernel: powernow-k8: 1 : pstate 1 (1600 MHz)
Jul 9 11:11:43 localhost kernel: powernow-k8: 2 : pstate 2 (1600 MHz)
Jul 9 11:11:43 localhost kernel: powernow-k8: 3 : pstate 3 (1600 MHz)
Jul 9 11:11:43 localhost kernel: powernow-k8: 4 : pstate 4 (1600 MHz)
Jul 9 11:11:43 localhost kernel: powernow-k8: 5 : pstate 5 (1600 MHz)
Why the CPU frequency is fixed? is it caused by BIOS setting?
Is there some methods to modify the limit in software not BIOS?
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-07-09 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 3:26 bugzilla-daemon [this message]
2015-11-18 12:33 ` [Bug 101241] cpufreq ondemand not work in my system bugzilla-daemon
2015-11-23 10:30 ` bugzilla-daemon
2015-12-14 23:10 ` [Bug 101241] cpufreq ondemand does not work on AMD GX-416RA SOC bugzilla-daemon
2016-08-23 9:34 ` bugzilla-daemon
2016-08-23 9:34 ` 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-101241-12968@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.