Comment 8 for bug 225319

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.