[2.6.27-7-generic] no cpufreq available

Bug #288592 reported by Thomas
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.27-7-generic

After Update from 2.6.27-6 to 2.6.27-7 my cpufreq not available more.

CPU is a Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz

root@nb:~# modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.27-7-generic/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device

root@nb:~# lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

Revision history for this message
Thomas (t.c) wrote :
Revision history for this message
Thomas (t.c) wrote :
Revision history for this message
Thomas (t.c) wrote :

root@nb:~# ls -lah /sys/devices/system/cpu/
insgesamt 0
drwxr-xr-x 5 root root 0 2008-10-24 09:10 .
drwxr-xr-x 12 root root 0 2008-10-24 09:10 ..
drwxr-xr-x 6 root root 0 2008-10-24 09:10 cpu0
drwxr-xr-x 5 root root 0 2008-10-24 09:10 cpu1
drwxr-xr-x 2 root root 0 2008-10-24 09:12 cpuidle
-r--r--r-- 1 root root 4,0K 2008-10-24 09:12 online
-r--r--r-- 1 root root 4,0K 2008-10-24 09:12 possible
-r--r--r-- 1 root root 4,0K 2008-10-24 09:12 present
-rw-r--r-- 1 root root 4,0K 2008-10-24 09:12 sched_mc_power_savings

root@nb:~# ls -lah /sys/devices/system/cpu/cpu0/
insgesamt 0
drwxr-xr-x 6 root root 0 2008-10-24 09:10 .
drwxr-xr-x 5 root root 0 2008-10-24 09:10 ..
drwxr-xr-x 5 root root 0 2008-10-24 09:12 cache
drwxr-xr-x 4 root root 0 2008-10-24 09:12 cpuidle
-r-------- 1 root root 4,0K 2008-10-24 09:12 crash_notes
drwxr-xr-x 2 root root 0 2008-10-24 09:12 thermal_throttle
drwxr-xr-x 2 root root 0 2008-10-24 09:12 topology

root@nb:~# ls -lah /sys/devices/system/cpu/cpu1
insgesamt 0
drwxr-xr-x 5 root root 0 2008-10-24 09:10 .
drwxr-xr-x 5 root root 0 2008-10-24 09:10 ..
drwxr-xr-x 5 root root 0 2008-10-24 09:12 cache
-r-------- 1 root root 4,0K 2008-10-24 09:12 crash_notes
-rw-r--r-- 1 root root 4,0K 2008-10-24 09:12 online
drwxr-xr-x 2 root root 0 2008-10-24 09:12 thermal_throttle
drwxr-xr-x 2 root root 0 2008-10-24 09:12 topology
root@nbtxc:~#

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Thomas,

Is there anything in your dmesg output after you try to modprobe acpi-cpufreq ? I'm not seeing any issues trying to modprobe this on 2.6.27-7.14 but I see you're on 2.6.27-7.13 based on your dmesg output.

ogasawara@emiko:~$ cat /proc/version_signature
Ubuntu 2.6.27-7.14-generic
ogasawara@emiko:~$ modinfo acpi-cpufreq
filename: /lib/modules/2.6.27-7-generic/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko
alias: acpi
license: GPL
description: ACPI Processor P-States Driver
author: Paul Diefenbaugh, Dominik Brodowski
srcversion: 09166B6001DCE2189668F16
depends: freq_table,processor
vermagic: 2.6.27-7-generic SMP mod_unload modversions 586
parm: acpi_pstate_strict:value 0 or non-zero. non-zero -> strict ACPI checks are performed during frequency changes. (uint)
ogasawara@emiko:~$ sudo modprobe acpi-cpufreq
ogasawara@emiko:~$ lsmod | grep "acpi_cpufreq"
acpi_cpufreq 15500 1
freq_table 12672 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
processor 42156 4 acpi_cpufreq,thermal
ogasawara@emiko:~$ ls -lah /sys/devices/system/cpu
total 0
drwxr-xr-x 5 root root 0 2008-10-24 12:02 .
drwxr-xr-x 11 root root 0 2008-10-24 12:02 ..
drwxr-xr-x 6 root root 0 2008-10-24 12:02 cpu0
drwxr-xr-x 5 root root 0 2008-10-24 12:02 cpu1
drwxr-xr-x 2 root root 0 2008-10-24 12:08 cpuidle
-r--r--r-- 1 root root 4.0K 2008-10-24 12:08 online
-r--r--r-- 1 root root 4.0K 2008-10-24 12:10 possible
-r--r--r-- 1 root root 4.0K 2008-10-24 12:10 present
-rw-r--r-- 1 root root 4.0K 2008-10-24 12:03 sched_mc_power_savings
ogasawara@emiko:~$ ls -lah /sys/devices/system/cpu/cpu0/
total 0
drwxr-xr-x 6 root root 0 2008-10-24 12:02 .
drwxr-xr-x 5 root root 0 2008-10-24 12:02 ..
drwxr-xr-x 5 root root 0 2008-10-24 12:08 cache
drwxr-xr-x 4 root root 0 2008-10-24 12:02 cpufreq
drwxr-xr-x 6 root root 0 2008-10-24 12:08 cpuidle
-r-------- 1 root root 4.0K 2008-10-24 12:02 crash_notes
drwxr-xr-x 2 root root 0 2008-10-24 12:08 topology
ogasawara@emiko:~$ ls -lah /sys/devices/system/cpu/cpu1/
total 0
drwxr-xr-x 5 root root 0 2008-10-24 12:02 .
drwxr-xr-x 5 root root 0 2008-10-24 12:02 ..
drwxr-xr-x 5 root root 0 2008-10-24 12:08 cache
lrwxrwxrwx 1 root root 0 2008-10-24 12:02 cpufreq -> ../cpu0/cpufreq
drwxr-xr-x 6 root root 0 2008-10-24 12:08 cpuidle
-r-------- 1 root root 4.0K 2008-10-24 12:02 crash_notes
-rw-r--r-- 1 root root 4.0K 2008-10-24 12:08 online
drwxr-xr-x 2 root root 0 2008-10-24 12:08 topology

Changed in linux:
status: New → Incomplete
Revision history for this message
Thomas (t.c) wrote :

there is no output in dmesg when I try to insert the acpi-cpufreq module. Any idea what's wrong?

Revision history for this message
Thomas (t.c) wrote :

ok.. i see, that the cpufreq was ok in kernel 2.6.27-7.10-generic

now in 2.6.27-7.13-generic it not working any more. see my dmesg output from bug 283132

http://launchpadlibrarian.net/18527510/dmesg-full

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Just curious if you've tested 2.6.27-7.14?

Revision history for this message
Thomas (t.c) wrote :

ok, sorry! I found the solution in my old report from kernel.org

http://bugzilla.kernel.org/show_bug.cgi?id=7578#c33

the BIOS becomes buggy again.. after load defaults, cpufreq is loading.

Sorry again for the wrong alarm :-)

Thomas

Changed in linux:
status: Incomplete → Invalid
Revision history for this message
graysky (da-audiophile) wrote :

Wow, this is EXACTLY what is happening with my Ubuntu 8.10 amd64 system except I could never get it to work properly.

It happens with the "stock" 2.6.27-7-generic kernel but also with the autoupdated 2.6.27-9-generic as well.
My CPU is an Intel(R) Xeon(R) CPU X3360.

# modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.27-9-generic/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device

# lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

I don't think it's problem with my BIOS because if I reboot into Debian/Lenny amd64, it works just fine. Does anyone have a suggestion?

Revision history for this message
Thomas (t.c) wrote :

@graysky

not at hook, but you can attach a full dmesg and we can look if we see something..

Revision history for this message
graysky (da-audiophile) wrote :
Download full text (48.1 KiB)

Here it is:

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.27-9-generic (buildd@yellow) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 22:15:32 UTC 2008 (Ubuntu 2.6.27-9.19-generic)
[ 0.000000] Command line: root=/dev/sdc1 ro quiet vga=773
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e400 (usable)
[ 0.000000] BIOS-e820: 000000000009e400 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfee0000 (usable)
[ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000cfef0000 - 00000000cff00000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
[ 0.000000] last_pfn = 0x130000 max_arch_pfn = 0x3ffffffff
[ 0.000000] last_pfn = 0xcfee0 max_arch_pfn = 0x3ffffffff
[ 0.000000] init_memory_mapping
[ 0.000000] 0000000000 - 00cfe00000 page 2M
[ 0.000000] 00cfe00000 - 00cfee0000 page 4k
[ 0.000000] kernel direct mapping tables up to cfee0000 @ 8000-e000
[ 0.000000] last_map_addr: cfee0000 end: cfee0000
[ 0.000000] init_memory_mapping
[ 0.000000] 0100000000 - 0130000000 page 2M
[ 0.000000] kernel direct mapping tables up to 130000000 @ c000-12000
[ 0.000000] last_map_addr: 130000000 end: 130000000
[ 0.000000] RAMDISK: 377ab000 - 37fef77c
[ 0.000000] DMI 2.5 present.
[ 0.000000] ACPI: RSDP 000F8700, 0014 (r0 IntelR)
[ 0.000000] ACPI: RSDT CFEE3000, 003C (r1 IntelR AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: FACP CFEE3080, 0074 (r1 IntelR AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: DSDT CFEE3100, 5720 (r1 INTELR AWRDACPI 1000 MSFT 3000000)
[ 0.000000] ACPI: FACS CFEE0000, 0040
[ 0.000000] ACPI: _HPT CFEE8900, 0038 (r1 IntelR AWRDACPI 42302E31 AWRD 98)
[ 0.000000] ACPI: _WDT CFEE8940, 0047 (r1 IntelR AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: MCFG CFEE89C0, 003C (r1 IntelR AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: APIC CFEE8840, 0084 (r1 IntelR AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: SSDT CFEE9320, 03A8 (r1 PmRef CpuPm 3000 INTL 20050309)
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-0000000130000000
[ 0.000000] Bootmem setup node 0 0000000000000000-0000000130000000
[ 0.000000] NODE_DATA [0000000000001000 - 0000000000005fff]
[ 0.000000] bootmap [000000000000d000 - 0000000000032fff] pages 26
[ 0.000000] (7 early reservations) ==> bootmem [0000000000 - 0130000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ ...

Revision history for this message
graysky (da-audiophile) wrote :

Here is an update. The problem definitely lies in the Ubuntu kernel.

I compiled my own kernel based on the Debian/Lenny config file. Upon rebooting, CPU scaling magically worked with no intervention on my part. This leads me to conclude that the amd64 kernel for Intrepid is tainted in some fashion such that what I describe in my first post happens!

How can I log this as a bug so the devteam can see it and hopefully fix it?

FYI, there is a great guide for compiling kernels under Ubuntu/Debian: http://technowizah.com/2005/12/debian-how-to-custom-kernel-compile.html

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi graysky, I'd recommend opening a new bug report. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.