This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
This affects me on a System76 PanP5 (Clevo M762TUN) on both Ubuntu and
Gentoo, both using 2.6.34 from the Ubuntu kernel PPA and the Gentoo
kernel sources, respectively.
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
This is also found on a Dell D800 laptop running Ubuntu Server 9.10.
Frequency is always stuck on the lowest (600 MHz).
The only way to disable it is to boot with acpi=off, but that induces other
problems, most notably the 'sensors' command no longer works.
Output of uname -a:
Linux walle
Update on my sitation:
I've removed the system fans and replaced them with oversized passive heatsinks.
When the bios doesn't detect the system fans, it disables SpeedStep and locks
the CPU frequency at its lowest value.
Re-connecting the fans does not help unless the computer is turned off and
I had the same problem with mine, where it was pegged at 2800Mhz.
(current policy: frequency should be within 2.80 GHz and 2.80 GHz.)
Try the following: For each of your processor cores:
Core 0:
sudo cpufreq-set -c 0 -d 800Mhz -u 2800Mhz
Core 1:
sudo cpufreq-set -c 1 -d 800Mhz -u 2800Mhz
etc.,
I have this problem with just one out of four cores.
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 800
Issue solved with thinkpad T43: BIOS settings reset/bios upgrade.
everything fine now.
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
You received this bug notification because you are a member of Ubuntu
Bugs,
Tested with current karmic dev version, happens there, too.
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Follow on from atany:
I also have a Dell M1330 running Jaunty. In addition to atany's
findings, I have found that after a suspend/resume or removal of AC
power, I can change the frequencies if the power is disconnected. On
reconnecting AC power the frequencies revert to 800MHz and I am unable
I can confirm this bug on Dell XPS M1330 using Jaunty upgraded from Intrepid
(which was working perfectly).
This happens to me not only after suspend/resume but also after I disconnect AC
power and then reconnect it. Frequency is then locked at 800MHz with no related
messages in logs.
As it
I don't know about T60p (yet, will keep an eye on it).
My issue is T43 - worked with intrepid, fails with jaunty. I already checked if
it could be temperature related, since that was my first suspect. But it didn't
look like that.
If it's temperature related what software is causing this, where
This should really be a high-priority bug. Running at 800 Mhz makes my
computer practically unusable for certain tasks, and forget multi-
tasking! It's extremely frustrating. I'm willing to help out with any
amount of debugging that I can provide, just let me know!
--
CPU frequency gets stuck
I've been running Jaunty on my T60p for sometime now and it seems to be a non
issue. Also be sure you keep the fan running or the CPU cool. I know if you
authorize the CPU Frequency Scaling Monitor 2.26.1 you can maunally set the CPU
speed or policy and it works well. Grag a copy of
I can confirm this behaviour as well with Thinkpad T43. Worked like a charm
with Intrepid, and is broken since upgrade to Jaunty. I tried
- clean reinstall
- AC power connected/disconnected
- changed permissions
The settings are correctly present in sys, but they do not have an
affect. (For some
I'm also seeing this on Jaunty (2.6.28-11-generic) on a Dell M1530. It's
inconsistent. It seems like it will suddenly start working for a while, and
then turn off again. Trying to change the setting has no effect.
/sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq is stuck at 80
--
Confirm the bug for me as well, on an updated 8.10 on a thinkpad T60.
also, this doesn't happen every time I suspend/resume, seems to show up quite
randomly.
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
You
This sounds like the same issue described here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288592
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
You received this bug notification because you are a
** Tags added: intrepid
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
T61 on 8.04 Hardy, seems to thrash between min and max values (2.0GHz
and 800MHz), even with the policy set to Performance. This happens for
both kpowersave and CPU Frequency Scaling Monitor 2.22.2
ARGH!
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad
I am also experiencing this problem. It is becoming very annoying. Every
time i come back to my computer, i have to switch my scaler back to
ondemand (it goes to performance mode for some reason) and i have to use
the command 'sudo cpufreq-set -d 80 sudo cpufreq-set -u 2534000'.
Has a fix
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Triaged
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
I can confirm this problem on a Thinkpad T60 Core2 T7200 with Ubuntu
8.10 2.6.27-9-generic. At boot, the CPU scales nicely, but when I set
the resolution for a second monitor in the gnome preferences, both CPU
are set to scale 1000MHz to 1000MHz reported in cpufreq-info.
--
CPU frequency gets
I get this problem on a desktop using a fresh install of Intrepid. CPU is
locked at the lowest frequency since original installation. The second cpu's
range is correct.
I have a Core2Duo E7200 @ 2.54Ghz and the first cpu is throttled at 1.6Ghz
cpufrequtils 002: cpufreq-info (C) Dominik
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm still getting this problem.
I'm using the current pre-release of 8.10 (as of 25 Sept. 2008), with kernel
version:
Linux socrates 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686
GNU/Linux
My hardware is a Dell D830, with an Intel Core2 T9500 processor.
If I sleep the laptop,
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
I'm seeing the same behavior with the following setup. Processor speed
remains fixed at 1000MHz, and cpufreq-info says current policy:
frequency should be within 1000 MHz and 1000 MHz. even though 2000MHz
are possible and I'm using the performance governor. Other governors
give me the same result.
I found the following very helpful (still testing):
http://setiathome.berkeley.edu/forum_thread.php?id=43189
gconf-editor may need to installed via yum. -George
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
I can confirm the same behavior on the following Fedora 8 32bit system:
Linux host 2.6.23.1-49.fc8 #1 SMP Thu Nov 8 21:41:26 EST 2007 i686 i686
i386 GNU/Linux
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU
On a thinkpad, the only way I found out how to have proper
suspend/resume working is by to have this:
In file /etc/acpi/suspend.d/10-thinkpad-standby-led.sh append this line
at the end:
/etc/init.d/powernowd stop
In file /etc/acpi/resume.d/90-thinkpad-unstandby-led.sh append this line at
Nope... the previous workaround does not worked. It scaled once, but
after next sleep/resume cycle it got stuck at 1Gz again...
Is anyone reading this?
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
You
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: cpufrequtils = linux-source-2.6.20
--
CPU frequency gets stuck at the lowest frequency after resume from suspend
(ThinkPad T60p)
https://bugs.launchpad.net/bugs/138465
You received this bug notification because you are a member of
** Tags added: cpu cpufrequtils frequency resume scaling suspend
** Description changed:
Binary package hint: cpufrequtils
+ Ubuntu Version: 7.04 (Feisty)
I have ThinkPad T60p with Core 2 Duo 2Gz CPU.
When the laptop wakes up after sleeping in standby mode, my CPU frequency
gets
33 matches
Mail list logo