'cpuinfo' says 9999 MHz & scaling not working on P4 laptop

[leopard]

Been tinkering with fresh install of the newest Ubuntu 8.04 on a Sager 5600D P4 2.53GHz laptop, 1GB RAM 40GB HD w/ ATI mobility Radeon 9000.
I can not get cpu scaling to operate. I have tried the default 'powernowd', 'cpudyn' and 'cpufreqd'. None seem to be working. When I install the frequency-applet in the top bar is shows I am running at 10.00GHz which is obviously wrong. I am brand spankin new to Linux/Ubuntu and don't know enough to dig around safely or even where to look. A great resource "Scott Scriven' on a forum has been walking me through a few things and he said it looks like a bug and I should report it, so here I am. I have not seen any other bug reports that look to be the same issue I am experiencing.

This is the output when I run the following commands
grep Hz /proc/cpuinfo
model name : Intel(R) Pentium(R) 4 CPU 2.53GHz
cpu MHz : 9999.000

/sys/devices/system/cpu/cpu0/cpufreq$ cat cpuinfo_min_freq cpuinfo_max_freq
9999000
9999000

/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_cur_freq
9999000

Please explicitly iterate any steps necessary to make any changes or retrieve any additional information you require from my system (remember Im a nOOb) ;-) .

Thanks for any assistance.

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Is this issue a regression from an earlier Ubuntu release?

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options):
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please run the command "sudo dmidecode > dmidecode.txt" and attach the resulting file "dmidecode.txt" to this bug report.
Thanks.

[leopard (ksavoie)]

1) Linux keith-laptop 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

[leopard (ksavoie)]

Sorry this is going in as multiple posts

00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 11)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 11)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801CA/CAM SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 01)
02:04.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:07.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
02:09.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
02:0a.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
02:0a.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
02:0a.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)

[Selene ToyKeeper (toykeeper)]

FWIW, the original question was posted here:
https://answers.launchpad.net/ubuntu/+question/31345
It doesn't say much that isn't already said here, but it's good to have these things linked together.

Leopard, could you boot an earlier Ubuntu release (LiveCD should be fine, no install required) and check /proc/cpuinfo again? Knowing whether this bug is in other versions really helps narrow down the search for the cause of the bug.

[leopard (ksavoie)]

Update/FYI

I booted Ubuntu 7.1 and ran
grep Hz /proc/cpuinfo and received the same info as 8.04
model name : Intel(R) Pentium(R) 4 CPU 2.53GHz
cpu MHz : 9999.000

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Thanks for the information.

Some initial thoughts follow.

From dmesg:
1/ Your PC appears to be a Clevo 5600D. Also marketed by Toshiba as a T40e & Sager 5600D (and probably others). Clevo is probably the manufacturer. This may help when your searching google for possible work-arounds.

2/ [ 23.527515] ACPI: Clevo 5600D detected - limiting to C2 max_cstate. Override with "processor.max_cstate=9"
      [ 23.527521] ACPI: processor limited to max C-state 2
      [ 23.527740] ACPI: CPU0 (power states: C1[C1] C2[C2])
      [ 23.527746] ACPI: Processor [CPU0] (supports 8 throttling states)
The first line here appears to be the result of a kernel patch. See here:
http://lkml.org/lkml/2006/1/4/331
This patch has been included as a work around for a locking-up problem with the Clevo 6500D.
This should not matter with regard to the issue you've reported but it's worth noting.

3/ dmesg shows:
       [ 20.926398] CPU0: Intel(R) Pentium(R) 4 CPU 2.53GHz stepping 04
       [ 20.926405] SMP motherboard not detected.
       [ 20.926408] Local APIC not detected. Using dummy APIC emulation.
       [ 20.926463] Brought up 1 CPUs
       [ 20.926484] CPU0 attaching sched-domain:
       [ 20.926488] domain 0: span 01
       [ 20.926490] groups: 01
       [ 20.926742] net_namespace: 64 bytes
I would assume that being a Pentium 4 that 2 CPUs were brought up. Perhaps Pentium 4s on laptops are structured differently??

While dmidecode shows:
      Handle 0x0004, DMI type 4, 35 bytes
      Processor Information
 Socket Designation: U49
 Type: Central Processor
 Family: Unknown
 Manufacturer: Intel
 ID: 24 0F 00 00 FF F9 EB 3F
 Version: A0
 Voltage: 1.8 V
 External Clock: Unknown
 Max Speed: 1500 MHz
 Current Speed: 2500 MHz
 Status: Populated, Enabled
 Upgrade: Slot 1
 L1 Cache Handle: 0x0005
 L2 Cache Handle: 0x0006
 L3 Cache Handle: Not Provided
 Serial Number: Not Specified
 Asset Tag: Not Specified
 Part Number: Not Specified
Note that max speed is less than current speed. This maybe causing confusion with apps attempting to deal with reporting or modifying throttling. Just a guess at this point.

It seems to me that these issues likely stem from a poorly constructed DSDT in BIOS.
Will pass on to the Kernel-ACPI Team for a closer look.

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Can you try booting with the following kernel option and report findings here?

1/ acpi=off

Thanks.

Passing to Ubuntu-Kernel-Team for further look.
While this maybe BIOS or acpi problem it is odd that a CPU freq. of 10GHz is reported. Can't see where this is coming from. As stated above it may be confusion as a result of "max speed" less than "current speed" (see dmidecode result).

[leopard (ksavoie)]

I booted Ubuntu 8.04 off the disc with acpi=off.
The CPU frequency applet now shows the frequency ACCURATELY at 2.53GHz.
When installing the applet I got a warning that CPU scaling is not supported. I have not seen this previously

grep Hz /proc/cpuinfo now says
model name : Intel(R) Pentium(R) 4 CPU 2.53GHz
cpu MHz : 2532.701

dmidecode.txt has not changed
Max Speed: 1500 MHz
Current Speed: 2500 MHz

dmesg.log has several entries under (maybe due to acpi being disabled?)
acpi_freq: Unknown symbol acpi_processor_notify_smm
acpi_freq: Unknown symbol acpi_processor_unregister_performance
acpi_freq: Unknown symbol acpi_processor_preregister_performance
acpi_freq: Unknown symbol acpi_processor_register_performance

Please be explicit on how to acquire any further requested info. (me nOOb) :-)

Thanks!

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Looks like a poorly constructed DSDT in BIOS.
Leaving with Kernel team for assessment.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

[leopard (ksavoie)]

I have tried the live cd of 8.10 and do not see any change to the CPU
frequency scaling.
It still reports the same as previous.

Thanks,
   Keith Savoie
   Vice President of Technology
   ACDT,ACPT,ACHDT

    L E O P A R D I N C
    ————————————————–
    m a r k e t i n g c o m m u n i c a t i o n s

   2679 Farnam, Suite 201
   Omaha, Nebraska 68131
   p: 402 422 0150 f: 402 422 0148
   leopard-inc.com

On Oct 16, 2008, at 1:08 PM, Ralph Janke wrote:

> The Intrepid Ibex 8.10 Beta release was most recently announced -
> http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27
> Ubuntu kernel. It would be great if you could test and verify if
> this is
> still an issue. The status is being set to Incomplete until we receive
> further feedback. Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> 'cpuinfo' says 9999 MHz & scaling not working on P4 laptop
> https://bugs.launchpad.net/bugs/225319
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Incomplete
>
> Bug description:
> Been tinkering with fresh install of the newest Ubuntu 8.04 on a
> Sager 5600D P4 2.53GHz laptop, 1GB RAM 40GB HD w/ ATI mobility
> Radeon 9000.
> I can not get cpu scaling to operate. I have tried the default
> 'powernowd', 'cpudyn' and 'cpufreqd'. None seem to be working. When
> I install the frequency-applet in the top bar is shows I am running
> at 10.00GHz which is obviously wrong. I am brand spankin new to
> Linux/Ubuntu and don't know enough to dig around safely or even
> where to look. A great resource "Scott Scriven' on a forum has been
> walking me through a few things and he said it looks like a bug and
> I should report it, so here I am. I have not seen any other bug
> reports that look to be the same issue I am experiencing.
>
> This is the output when I run the following commands
> grep Hz /proc/cpuinfo
> model name : Intel(R) Pentium(R) 4 CPU 2.53GHz
> cpu MHz : 9999.000
>
> /sys/devices/system/cpu/cpu0/cpufreq$ cat cpuinfo_min_freq
> cpuinfo_max_freq
> 9999000
> 9999000
>
> /sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_cur_freq
> 9999000
>
> Please explicitly iterate any steps necessary to make any changes or
> retrieve any additional information you require from my system
> (remember Im a nOOb) ;-) .
>
> Thanks for any assistance.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[kernel-janitor (kernel-janitor)]

Hi ksavoie,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 225319

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]