Michael DePaulo, thank you for reporting this and helping make Ubuntu better.
Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If
so,
I have been experiencing something with very similar symptoms to this on
a Dell Latitude E6410 laptop with Ubuntu 12.04. Looking in
/sys/devices/system/cpu/cpu*/cpufreq showed that the CPU frequencies
were always stuck at just under half what they could do, no matter the
load. After finding this
The requested information has been provided.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: cpufreqd (Ubuntu)
Status: New = Confirmed
** Tags removed: cpu cpufreq frequency scaling
** Also affects: linux via
** Changed in: linux
Status: Unknown = Fix Released
** Changed in: linux
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/637845
Title:
[maverick] CPU frequency
look at the page
http://www.thinkwiki.org/wiki/Problem_with_CPU_frequency_scaling. Ther's
described solvation of problem with lenovo but it can be the same
mechanism. My cpu ran constantly on lower speed and after making
described solution now it's ok.
--
You received this bug notification
Somehow my system started behaving normally on battery after a boot into
Windows 7. Any suggestions for what could be wrong?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/637845
Title:
[maverick]
I don't know if my issue is related here.
Ondemand and any scaling works fine for me when I run on AC power, but when I
run on battery only, the cpu behaves strangely and very rarely scales up. Even
if I load a flash game in my browser it stays at 800 mhz on the core running
the object.
But it's not the only thing. My previous observation was made with my battery
plugged
on my laptop, with AC/DC power. Another day, without battery, I was very
surprised when I saw that the bios_limit was still stuck to 1.20GHz (!). I
think it's a BIOS related problem. But fortunately,
In my case, I solved this problem with BIOS configuration. In my BIOS I
set Performance profile instead of Power-Saving for AC/DC and
Battery Mode. Result : bios_limit returns now 2.40 GHz instead of
1.20GHz, and cpufreq can do his job. (Tested with 2.6.36 kernel too).
--
[maverick] CPU
I had a similar problem on my Asus U43JC which runs on an Intel i5-450m
(using Ubuntu 10.10). The BIOS would limit my frequence at 1.2GHz, no
matter what cpufreq governor I was using, no matter if on the power cord
or on the battery. To fix this, I added processor.ignore_ppc=1 to the
kernel boot
When I ran two instances of burnK7 my cpu did not step up from 800 GHz,
but last night when I was watching a video on iPlayer I noticed that it
did start stepping up (top reported *over* 100% CPU usage). If anyone
can explain how I can test this bug I would be happy to do so.
--
[maverick] CPU
I'm seeing this too with my AMD K325.
** Attachment added: cpufreq-info.txt
https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/637845/+attachment/1709176/+files/cpufreq-info.txt
--
[maverick] CPU frequency does not scale up unless all cores are in use
cpu info
** Attachment added: cpuinfo.txt
https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/637845/+attachment/1709177/+files/cpuinfo.txt
--
[maverick] CPU frequency does not scale up unless all cores are in use
https://bugs.launchpad.net/bugs/637845
You received this bug notification
Hey Jeremy,
I installed the latest upstream linux-image package and its two headers
package. The linux image package is as follows:
linux-image-2.6.36-020636-generic_2.6.36-020636.201010210905_amd64.deb
I then ran the same test as before with this upstream kernel, and the
frequency problem is
Hi Michael,
If you could also please test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
[maverick] CPU frequency does not scale up unless all cores are in use
https://bugs.launchpad.net/bugs/637845
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After a bit more digging I discovered something interesting. When
idling, the CPU has the full range of frequencies available to it, from
min to max. But, when the load ramps up, the BIOS appears to step in
and limit the frequency, then ACPI throttling steps in.
I used a simple script
I have a very similar problem with my core i5 520 M (2 cores, 4 threads).
But, not as the previous case, my CPU never scales up. In fact I never manage
to make it scale, it is always blocked to the lowest frequency.
For me, it may be a kernel problem. With the stock kernel provide by Maverick
I have just tested with a fresh custom kernel 2.6.35.7 (from kernel.org).
The behavior is the same as the 2.6.35.4 Maverick Kernel.
--
[maverick] CPU frequency does not scale up unless all cores are in use
https://bugs.launchpad.net/bugs/637845
You received this bug notification because you are
I am getting the same behavior after upgrading to maverick with my Core
2 Duo T7200. Stuck at 1.00 GHz (minimum frequency) no mater what the
stress level. Should be at 2.00 GHz.
--
[maverick] CPU frequency does not scale up unless all cores are in use
https://bugs.launchpad.net/bugs/637845
You
The bug has been notified here too :
https://bugzilla.kernel.org/show_bug.cgi?id=19702
** Bug watch added: Linux Kernel Bug Tracker #19702
http://bugzilla.kernel.org/show_bug.cgi?id=19702
--
[maverick] CPU frequency does not scale up unless all cores are in use
On the reported bug from the link below, a patch has been provided. I
have just tested it with a custom kernel 2.6.35.7, but unfortunately, it
did not give any good result with my core i5 520 M.
cpufreq-info always return :
current policy: frequency should be within 1.20 GHz and 1.20 GHz.
The
22 matches
Mail list logo