Bug 10383
Summary: | CPU FREQ policy value scaling_max_freq gets stuck at 800MHz on core2duo | ||
---|---|---|---|
Product: | Power Management | Reporter: | Ralf Kaestner (ralf.kaestner) |
Component: | cpufreq | Assignee: | Thomas Renninger (trenn) |
Status: | CLOSED DUPLICATE | ||
Severity: | normal | CC: | alex, lenb, ralf.kaestner |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.24 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
cpufreq-info when the problem is visible
cpufreq-info called multiple times showing the down-scaling of the policy dmesg without debug data dmesg output with cpufreq-debug=7 dump of the related sysfs parts content of /proc/acpi/dsdt output of acpidump (hex data) the suspicious acpi table error extracted from dmesg/messages content of /proc/cpuinfo |
Description
Ralf Kaestner
2008-04-02 10:41:32 UTC
Created attachment 15572 [details]
cpufreq-info when the problem is visible
Created attachment 15573 [details]
cpufreq-info called multiple times showing the down-scaling of the policy
Created attachment 15574 [details]
dmesg without debug data
Created attachment 15575 [details]
dmesg output with cpufreq-debug=7
Created attachment 15576 [details]
dump of the related sysfs parts
Created attachment 15577 [details]
content of /proc/acpi/dsdt
Created attachment 15578 [details]
output of acpidump (hex data)
Created attachment 15579 [details]
the suspicious acpi table error extracted from dmesg/messages
Created attachment 15580 [details]
content of /proc/cpuinfo
Smells like the same problem I'm suffering: http://bugzilla.kernel.org/show_bug.cgi?id=9919 thanks a lot for that info, sounds very similar. acpi_osi=!Window2006 as kernel arg sounds as a nice workaround to me, will try that right now, or are there any gotchas that I've missed? looks like "bingo" you made my day buddy! giving acpi_osi="!Window2006" as kernel arg fixes the problem. WARNING WILL ROBINSON DANGER DANGER This is not a fix at least on my laptop. Suspend/Resume one works for one cycle, I lose the cute beeps of the ACPI bits and some other ACPI functionality goes icky. Worth making sure you can still do anything. I personally prefer to be able to suspend/resume over get 400Mhz higher speeds on a nasty x86 box... :) thx, I got that, anyhow - suspend/resume is not even working at all on my laptop (will test that later) So I will test this Anti-V*sta option for a while and leave the bug open as reference. kernel dev may decide to close it as duplicate of 9919. However, seems that the Lifebook W 8010 needs some blacklisting as well. The acpi table error mentioned in comment #8 is gone with putting the acpi_osi option in. The message: ACPI Error (tbinstal-0134): Table has invalid signature [ ], must be SSDT, PSDT or OEMx [20070126] Comes from the visit table (see the other bug)which is missing the "SSDT" in the table header. This is clearly a BIOS bug. The table is not loaded when osi=!Winows 2006 is passed. These machines are so similar, I mark the bugs as duplicates now. *** This bug has been marked as a duplicate of bug 9919 *** |