** 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 stuck in the lowest possible mode: 1Gz. I know that this is CPU frequency 
scaling module who's doing that. I tried to change many different variables: 
running on AC power vs battery, switching between governors (ondemand, 
conservative) - nothing helps. It wakes up and does not scale from 1Gz. (I know 
how to force CPU go up to 2Gz even with conservative governor - I run several 
instances of glxgears).
  
  Below is the output from cpufreq-info, as you can see it says
  [I]"frequency should be within 1000 MHz and 1000 MHz"[/I]. It correctly
  reports hardware max. limit of 2GHz, but [B]cpufreq thinks that the
  upper allowed frequency limit is only 1Gz[/B]!!!
  
  [CODE]cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
  Report errors and bugs to [EMAIL PROTECTED], please.
  analyzing CPU 0:
    driver: acpi-cpufreq
    CPUs which need to switch frequency at the same time: 0 1
    hardware limits: 1000 MHz - 2.00 GHz
    available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
    available cpufreq governors: conservative, performance
    current policy: frequency should be within 1000 MHz and 1000 MHz.
                    The governor "conservative" may decide which speed to use
                    within this range.
    current CPU frequency is 1000 MHz (asserted by call to hardware).
  analyzing CPU 1:
    driver: acpi-cpufreq
    CPUs which need to switch frequency at the same time: 0 1
    hardware limits: 1000 MHz - 2.00 GHz
    available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
    available cpufreq governors: conservative, performance
    current policy: frequency should be within 1000 MHz and 1000 MHz.
                    The governor "conservative" may decide which speed to use
                    within this range.
    current CPU frequency is 1000 MHz (asserted by call to hardware).
  [/CODE]
  
  If I reboot everything goes back to normal. CPU scales up and the output
  above says "should be withtin 1000 MHz and 2 GHz".
  
  I have been trying to fix it myself. For instance I added the following to 
/etc/default/acpi-support (trying to reload CPU scaling kernel modules on 
suspend/resume):
  [CODE]MODULES="cpufreq_stats cpufreq_conservative acpi-cpufreq"[/CODE]
  
  It did not help. 
  Then I tried 
  [CODE]sudo cpufreq-set -u 2000000
  or
  sudo cpufreq-set -u 2GHz[/CODE]
  Those did not do anything either - CPU still could not get up to 2Gz.
  
  Also I wet to /sys/devices/system/cpu and run these commands as root:
  
  [CODE]echo 2000000 > cpu0/cpufreq/scaling_max_freq
  echo 2000000 > cpu1/cpufreq/scaling_max_freq
  [/CODE]
  
  ... and nothing happens. Those two files still say 1000000. Normally
  (after reboot) they report 2000000 and I can write other values into
  them. At this point I am not sure what else can I try. Obviously I
  should update wakeup/resume scripts with some commands to bitch-slap cpu
  frequency scaling module, but I cannot figure out what to do.
  
  Here is my /etc/default/cpufrequtils
  [CODE]ENABLE="true"
  GOVERNOR="conservative"
  MIN_SPEED=1000000
  MAX_SPEED=2000000
  [/CODE]
  
  Here is my /etc/modules
  [CODE]lp
  
  cpufreq_stats
  cpufreq_ondemand
  cpufreq_conservative
  cpufreq_powersave
  acpi-cpufreq  # this is what Core 2 Duo needs. 
  
  fuse
  [/CODE]
  
  This is very frustrating. I spent 5 hours last night trying to figure
  this out...

** 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 stuck in the lowest possible mode: 1Gz. I know that this is CPU frequency 
scaling module who's doing that. I tried to change many different variables: 
running on AC power vs battery, switching between governors (ondemand, 
conservative) - nothing helps. It wakes up and does not scale from 1Gz. (I know 
how to force CPU go up to 2Gz even with conservative governor - I run several 
instances of glxgears).
  
- Below is the output from cpufreq-info, as you can see it says
- [I]"frequency should be within 1000 MHz and 1000 MHz"[/I]. It correctly
- reports hardware max. limit of 2GHz, but [B]cpufreq thinks that the
- upper allowed frequency limit is only 1Gz[/B]!!!
+ Below is the output from cpufreq-info, as you can see it says "frequency
+ should be within 1000 MHz and 1000 MHz"[/I]. It correctly reports
+ hardware max. limit of 2GHz, but cpufreq thinks that the upper allowed
+ frequency limit is only 1Gz!!!
  
- [CODE]cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
+ -----------------------------------------------------------------------
+ cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
  Report errors and bugs to [EMAIL PROTECTED], please.
  analyzing CPU 0:
    driver: acpi-cpufreq
    CPUs which need to switch frequency at the same time: 0 1
    hardware limits: 1000 MHz - 2.00 GHz
    available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
    available cpufreq governors: conservative, performance
    current policy: frequency should be within 1000 MHz and 1000 MHz.
                    The governor "conservative" may decide which speed to use
                    within this range.
    current CPU frequency is 1000 MHz (asserted by call to hardware).
  analyzing CPU 1:
    driver: acpi-cpufreq
    CPUs which need to switch frequency at the same time: 0 1
    hardware limits: 1000 MHz - 2.00 GHz
    available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
    available cpufreq governors: conservative, performance
    current policy: frequency should be within 1000 MHz and 1000 MHz.
                    The governor "conservative" may decide which speed to use
                    within this range.
    current CPU frequency is 1000 MHz (asserted by call to hardware).
- [/CODE]
+ -----------------------------------------------------------------------
  
  If I reboot everything goes back to normal. CPU scales up and the output
  above says "should be withtin 1000 MHz and 2 GHz".
  
  I have been trying to fix it myself. For instance I added the following to 
/etc/default/acpi-support (trying to reload CPU scaling kernel modules on 
suspend/resume):
- [CODE]MODULES="cpufreq_stats cpufreq_conservative acpi-cpufreq"[/CODE]
+ MODULES="cpufreq_stats cpufreq_conservative acpi-cpufreq"
  
  It did not help. 
  Then I tried 
- [CODE]sudo cpufreq-set -u 2000000
+ sudo cpufreq-set -u 2000000
  or
- sudo cpufreq-set -u 2GHz[/CODE]
+ sudo cpufreq-set -u 2GHz
  Those did not do anything either - CPU still could not get up to 2Gz.
  
  Also I wet to /sys/devices/system/cpu and run these commands as root:
  
- [CODE]echo 2000000 > cpu0/cpufreq/scaling_max_freq
+ echo 2000000 > cpu0/cpufreq/scaling_max_freq
  echo 2000000 > cpu1/cpufreq/scaling_max_freq
- [/CODE]
  
  ... and nothing happens. Those two files still say 1000000. Normally
  (after reboot) they report 2000000 and I can write other values into
  them. At this point I am not sure what else can I try. Obviously I
  should update wakeup/resume scripts with some commands to bitch-slap cpu
  frequency scaling module, but I cannot figure out what to do.
  
  Here is my /etc/default/cpufrequtils
- [CODE]ENABLE="true"
+ 
+ -----------------------------------------------------------------------
+ ENABLE="true"
  GOVERNOR="conservative"
  MIN_SPEED=1000000
  MAX_SPEED=2000000
- [/CODE]
+ -----------------------------------------------------------------------
  
  Here is my /etc/modules
- [CODE]lp
+ -----------------------------------------------------------------------
+ lp
  
  cpufreq_stats
  cpufreq_ondemand
  cpufreq_conservative
  cpufreq_powersave
  acpi-cpufreq  # this is what Core 2 Duo needs. 
  
  fuse
- [/CODE]
+ -----------------------------------------------------------------------
  
  This is very frustrating. I spent 5 hours last night trying to figure
  this out...

-- 
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 the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to