From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
Date: Wed, 11 Sep 2013 19:49:59 +0000 [thread overview]
Message-ID: <bug-60839-12968-hmGdm1A9oY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60839-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60839
--- Comment #6 from Sven Köhler <sven.koehler@gmail.com> ---
Nope, the patch didn't help. Here's the bash-code I used to test:
cmax=$(cat cpuinfo_max_freq)
echo $cmax >scaling_max_freq
bmax=$cmax
while [ $bmax -ge $cmax ]; do
bmax=$(cat bios_limit)
smax=$(cat scaling_max_freq)
echo $cmax >scaling_max_freq
echo $bmax $smax
done
while true; do
echo $(cat bios_limit) $(cat scaling_max_freq)
sleep 0.5
done
The output is like this:
2534000 2534000
2534000 2534000
2534000 2534000
2534000 2534000
2534000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1333000 1199000
1333000 1199000
1333000 1199000
1333000 1199000
1466000 1199000
1466000 1199000
As you can see, scaling_max_freq remains low. When the script is not running,
scaling_max_freq increases along with bios_limit.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-09-11 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 12:47 [Bug 60839] New: scaling_max_freq cannot be set to values larger than bios_limit bugzilla-daemon
2013-09-10 8:28 ` [Bug 60839] " bugzilla-daemon
2013-09-10 8:36 ` bugzilla-daemon
2013-09-10 9:46 ` bugzilla-daemon
2013-09-10 12:45 ` bugzilla-daemon
2013-09-10 13:15 ` bugzilla-daemon
2013-09-10 14:19 ` bugzilla-daemon
2013-09-11 19:49 ` bugzilla-daemon [this message]
2013-09-12 14:07 ` bugzilla-daemon
2013-09-12 14:49 ` bugzilla-daemon
2013-09-18 3:27 ` bugzilla-daemon
2013-10-14 7:58 ` 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-60839-12968-hmGdm1A9oY@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