Bug 20422 - scaling_max_freq stuck at 600000 - Dell Inspiron 8600
Summary: scaling_max_freq stuck at 600000 - Dell Inspiron 8600
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-16 22:38 UTC by lionel jousset
Modified: 2010-11-08 02:27 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.35/36
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
Output of cpuinfo, cpufreq-info, lspci, modules and ioports. (17.36 KB, text/plain)
2010-10-16 22:38 UTC, lionel jousset
Details

Description lionel jousset 2010-10-16 22:38:23 UTC
Created attachment 33772 [details]
Output of cpuinfo, cpufreq-info, lspci, modules and ioports.

Hi,
I'm running an ubuntu 10.10 on my laptop Inspiron 8600,
it doesn't scale its cpu frequency, that's "current policy" in cpufreq-info wich is wrong:
"current policy: frequency should be within 600 MHz and 600 MHz."
the cpu is is blocked to 600 MHz and "cpufreq-set" can set anything.
I try to fix it in /etc/sysfs.conf but no way...
It doesn't work with kernel 2.6.35 but I have tested too the kernel found on:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-rc7-maverick/
(http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-10-16-maverick/ also)

The lastest bios was already on board and I ran a live cd 
ubuntu 10.4 with 2.6.32-24 kernel and frequency scaling worked well.

In the attachment, there is cpuinfo, cpufreq-info, lspci, modules and ioports.
I hope that it will help.

Thanks.
Lionel
Comment 1 lionel jousset 2010-10-16 22:51:06 UTC
the output of "grep . /sys/devices/system/cpu/cpu0/cpufreq/*"
gave:
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1700000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:10000
/sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1700000 1600000 1400000 1200000 1000000 800000 600000 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:conservative ondemand userspace powersave performance 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:ondemand
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>


scaling_setspeed:<unsupported>
in fact I don't know if my bug report is at the right place.

Lionel
Comment 2 ykzhao 2010-10-19 00:52:41 UTC
Will you please add the boot option of "cpufreq.debug=0x07" and attach the output of dmesg?
Please also attach the output of acpidump, /proc/cpuinfo.

Thanks.
Comment 3 Zhang Rui 2010-10-19 01:33:02 UTC
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:600000

someone sets the cpu p-state limit.

what's the kernel version of ubuntu 10.10? there should be a "bios_limit" file at /sys/devices/system/cpu/cpu0/cpufreq/.

does the problem still exists if you build in the processor driver and boot with processor.ignore_ppc?
Comment 4 Zhang Rui 2010-10-29 07:05:29 UTC
ping...
Comment 5 Zhang Rui 2010-11-08 02:27:07 UTC
Bug closed as there is no response from the bug reporter.
Please feel free to re-open it at any time if the problem can be reproduced in the LATEST upstream kernel.

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