Bug 11033 - CPU scaling not working on Centrino based laptop
Summary: CPU scaling not working on Centrino based laptop
Status: REJECTED WILL_NOT_FIX
Alias: None
Product: ACPI
Classification: Unclassified
Component: ACPICA-Core (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: ykzhao
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-03 13:19 UTC by Olivier Devillard
Modified: 2008-07-14 01:24 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.22 and 2.6.24 at least
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
acpidump on kernel 2.6.20 (72.62 KB, text/plain)
2008-07-04 13:48 UTC, Olivier Devillard
Details
acpidump on kernel 2.6.22 (72.62 KB, text/plain)
2008-07-04 13:48 UTC, Olivier Devillard
Details
acpidump on kernel 2.6.24 (72.62 KB, text/plain)
2008-07-04 13:49 UTC, Olivier Devillard
Details
Working Kernel dmesg (2.6.20-17-generic) (26.91 KB, text/plain)
2008-07-09 12:15 UTC, Olivier Devillard
Details
Non-working Kernel dmesg (2.6.20.21-custom) (94.59 KB, text/plain)
2008-07-09 12:17 UTC, Olivier Devillard
Details

Description Olivier Devillard 2008-07-03 13:19:28 UTC
Latest working kernel version:2.6.20 (Ubuntu 7.04)
Earliest failing kernel version:2.6.22 (Ubuntu 7.10)
Distribution:Current is Ubuntu 8.04 (2.6.24)
Hardware Environment: Laptop: Fujitsu Siemens - Amilo M1425 (CPU = Centrino)
Software Environment: Ubuntu Hardy
Problem Description:
CPU Scaling does not work anymore. Frequency should be 1.70 GHz but is stuck at 600 MHz. I think that newer versions get their information from the BIOS, whereas earlier versions got their information from another place.

Steps to reproduce:
sudo modprobe acpi-cpufreq
gives the following message ==> 
FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.24-19-386/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device
The same message is displayed for all other cpufreq modules.
Comment 1 ykzhao 2008-07-03 19:48:02 UTC
Hi, Oliview
   Will you please confirm whether the cpu scaling can work on the 2.6.20 kernel?
   Please attach the output of acpidump.
   Will you please enable "CONFIG_CPUFREQ_DEBUG" in kernel configuration and add the boot option of "cpufreq.debug=7"?
   After the system is booted , please try to load the acpi_cpufreq driver and attach the output of dmesg. ( both 2.6.20 and 2.6.22 are required).
   Thanks.
Comment 2 Olivier Devillard 2008-07-04 13:48:26 UTC
Created attachment 16738 [details]
acpidump on kernel 2.6.20
Comment 3 Olivier Devillard 2008-07-04 13:48:59 UTC
Created attachment 16739 [details]
acpidump on kernel 2.6.22
Comment 4 Olivier Devillard 2008-07-04 13:49:29 UTC
Created attachment 16740 [details]
acpidump on kernel 2.6.24
Comment 5 Olivier Devillard 2008-07-04 13:54:09 UTC
Hi ykzhao,

I confirm that CPU scaling can work on the 2.6.20 kernel.

I have attached for your reference the acpidump for 2.6.20, 2.6.22 and 2.6.24.

I know you want the output of 2.6.20 and 2.6.22, but this will be more complicated and lengthy, as I can only boot from CD at the moment and it is difficult to enable kernel options. I will need to find some hard disk and re-install previous versions. I should be able to come back to you during next week.

Thank you for your help.
Comment 6 ykzhao 2008-07-06 19:47:24 UTC
Hi, Oliver
   thanks for the acpidump info. In fact the acpidump is not related with the OS kernel. So you needn't attach the acpidump obtained on the different kernel.
    
   From the acpidump there doesn't exist the following object related with acpi-cpufreq driver.
   _PSS, _PCT, _PPC
   So when the acpi-cpuferq driver is loaded, OS will report the following warning message:
  > FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.24-19-386/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko):
No such device

  Anyway, please add the boot option of "cpufreq.debug=7" and attach the output of dmesg.(Both 2.6.20 and 2.6.24 are required).
  Thanks.

   
Comment 7 Olivier Devillard 2008-07-07 14:24:33 UTC
Hi YKZhao,

the boot option of "cpufreq.debug=7" is not recognized by default Ubuntu kernel. I need to recompile the kernel before I can do the testing (which can take some time with the CPU frequency set low), but should be able to come back to you before end of the week.
Comment 8 Olivier Devillard 2008-07-09 12:15:08 UTC
Created attachment 16774 [details]
Working Kernel dmesg (2.6.20-17-generic)

This is the output of dmesg on a working kernel (2.6.20-17-generic).

It seems the module loaded is "speedstep-centrino".
Comment 9 Olivier Devillard 2008-07-09 12:17:09 UTC
Created attachment 16775 [details]
Non-working Kernel dmesg (2.6.20.21-custom)

This is the output of dmesg on a non-working kernel (2.6.20.21), compiled with the correct flag and booted with the option "cpufreq.debug=7".

Neither "acpi-cpufreq" nor "speedstep-centrino" can be loaded as modules.
Comment 10 Olivier Devillard 2008-07-09 13:03:47 UTC
Hi YKZhao,

I hope this is enough for your information.
Thanks in advance for your help.
Comment 11 Olivier Devillard 2008-07-09 15:08:47 UTC
Hi YKZhao,

I found a solution, based on the following page:
http://www.amilo-forum.com/topic,1808,-CPU-stuck-at-600Mhz.html

I understand:

1) kernel 2.6.20 was specific to Ubuntu. A patch indicated available cpu frequencies.
2) in generic and later ubuntu kernels, available frequencies were given by the bios.

The regression problem is therefore Ubuntu, and not a generic kernel problem, aggravated by a bios problem on the kind of laptop I use (Amilo M1425).

I think you can close the bug.

Thank you very much for your support.
Comment 12 ykzhao 2008-07-09 23:52:15 UTC
Hi, Olivier
   Thanks for the info.
   Will you please use the "speedstep-centrino" driver on the 2.6.22 kernel and see whether the cpufreq still can't work?
   Thanks.
Comment 13 Olivier Devillard 2008-07-12 08:39:57 UTC
Hi YKZhao,

I cannot load the speedstep-centrino. I get the same message I got with acpi-cpufreq: FATAL:... no such device.

I hope this helps.
Comment 14 ykzhao 2008-07-14 01:24:11 UTC
Hi, Olivier
    Thanks for your work. From the comment #11 it seems that the problem is related with the bios problem and not a generic kernel problem. 
    So the bug will be rejected.

Note You need to log in before you can comment on or make changes to this bug.