https://bugzilla.novell.com/show_bug.cgi?id=579932
https://bugzilla.novell.com/show_bug.cgi?id=579932#c50
--- Comment #50 from Andreas Nordal 2011-01-28 15:11:55 UTC ---
It was not hard to tell that "processor.max_cstate=1" worked and
"processor.max_cstate=2" did not. Below is the output of "grep . -r
/sys/devices/system/cpu/cpu0/cpuidle/" under the various kernel commands:
With nolapic_timer:
/sys/devices/system/cpu/cpu0/cpuidle/state0/name:C0
/sys/devices/system/cpu/cpu0/cpuidle/state0/desc:CPUIDLE CORE POLL IDLE
/sys/devices/system/cpu/cpu0/cpuidle/state0/latency:0
/sys/devices/system/cpu/cpu0/cpuidle/state0/power:4294967295
/sys/devices/system/cpu/cpu0/cpuidle/state0/usage:221938
/sys/devices/system/cpu/cpu0/cpuidle/state0/time:538117852
/sys/devices/system/cpu/cpu0/cpuidle/state1/name:C1
/sys/devices/system/cpu/cpu0/cpuidle/state1/desc:ACPI FFH INTEL MWAIT 0x0
/sys/devices/system/cpu/cpu0/cpuidle/state1/latency:1
/sys/devices/system/cpu/cpu0/cpuidle/state1/power:1000
/sys/devices/system/cpu/cpu0/cpuidle/state1/usage:0
/sys/devices/system/cpu/cpu0/cpuidle/state1/time:0
/sys/devices/system/cpu/cpu0/cpuidle/state2/name:C2
/sys/devices/system/cpu/cpu0/cpuidle/state2/desc:ACPI FFH INTEL MWAIT 0x10
/sys/devices/system/cpu/cpu0/cpuidle/state2/latency:1
/sys/devices/system/cpu/cpu0/cpuidle/state2/power:500
/sys/devices/system/cpu/cpu0/cpuidle/state2/usage:0
/sys/devices/system/cpu/cpu0/cpuidle/state2/time:0
/sys/devices/system/cpu/cpu0/cpuidle/state3/name:C3
/sys/devices/system/cpu/cpu0/cpuidle/state3/desc:ACPI FFH INTEL MWAIT 0x50
/sys/devices/system/cpu/cpu0/cpuidle/state3/latency:162
/sys/devices/system/cpu/cpu0/cpuidle/state3/power:100
/sys/devices/system/cpu/cpu0/cpuidle/state3/usage:0
/sys/devices/system/cpu/cpu0/cpuidle/state3/time:0
With processor.max_cstate=1:
/sys/devices/system/cpu/cpu0/cpuidle/: No such file or directory
With processor.max_cstate=2:
/sys/devices/system/cpu/cpu0/cpuidle/state0/name:C0
/sys/devices/system/cpu/cpu0/cpuidle/state0/desc:CPUIDLE CORE POLL IDLE
/sys/devices/system/cpu/cpu0/cpuidle/state0/latency:0
/sys/devices/system/cpu/cpu0/cpuidle/state0/power:4294967295
/sys/devices/system/cpu/cpu0/cpuidle/state0/usage:114
/sys/devices/system/cpu/cpu0/cpuidle/state0/time:52416
/sys/devices/system/cpu/cpu0/cpuidle/state1/name:C1
/sys/devices/system/cpu/cpu0/cpuidle/state1/desc:ACPI FFH INTEL MWAIT 0x0
/sys/devices/system/cpu/cpu0/cpuidle/state1/latency:1
/sys/devices/system/cpu/cpu0/cpuidle/state1/power:1000
/sys/devices/system/cpu/cpu0/cpuidle/state1/usage:9212
/sys/devices/system/cpu/cpu0/cpuidle/state1/time:598101
/sys/devices/system/cpu/cpu0/cpuidle/state2/name:C2
/sys/devices/system/cpu/cpu0/cpuidle/state2/desc:ACPI FFH INTEL MWAIT 0x10
/sys/devices/system/cpu/cpu0/cpuidle/state2/latency:1
/sys/devices/system/cpu/cpu0/cpuidle/state2/power:500
/sys/devices/system/cpu/cpu0/cpuidle/state2/usage:398553
/sys/devices/system/cpu/cpu0/cpuidle/state2/time:195062754
With no workaround:
/sys/devices/system/cpu/cpu0/cpuidle/state0/name:C0
/sys/devices/system/cpu/cpu0/cpuidle/state0/desc:CPUIDLE CORE POLL IDLE
/sys/devices/system/cpu/cpu0/cpuidle/state0/latency:0
/sys/devices/system/cpu/cpu0/cpuidle/state0/power:4294967295
/sys/devices/system/cpu/cpu0/cpuidle/state0/usage:4857
/sys/devices/system/cpu/cpu0/cpuidle/state0/time:83419
/sys/devices/system/cpu/cpu0/cpuidle/state1/name:C1
/sys/devices/system/cpu/cpu0/cpuidle/state1/desc:ACPI FFH INTEL MWAIT 0x0
/sys/devices/system/cpu/cpu0/cpuidle/state1/latency:1
/sys/devices/system/cpu/cpu0/cpuidle/state1/power:1000
/sys/devices/system/cpu/cpu0/cpuidle/state1/usage:78437
/sys/devices/system/cpu/cpu0/cpuidle/state1/time:5581403
/sys/devices/system/cpu/cpu0/cpuidle/state2/name:C2
/sys/devices/system/cpu/cpu0/cpuidle/state2/desc:ACPI FFH INTEL MWAIT 0x10
/sys/devices/system/cpu/cpu0/cpuidle/state2/latency:1
/sys/devices/system/cpu/cpu0/cpuidle/state2/power:500
/sys/devices/system/cpu/cpu0/cpuidle/state2/usage:1320758
/sys/devices/system/cpu/cpu0/cpuidle/state2/time:262335334
/sys/devices/system/cpu/cpu0/cpuidle/state3/name:C3
/sys/devices/system/cpu/cpu0/cpuidle/state3/desc:ACPI FFH INTEL MWAIT 0x50
/sys/devices/system/cpu/cpu0/cpuidle/state3/latency:162
/sys/devices/system/cpu/cpu0/cpuidle/state3/power:100
/sys/devices/system/cpu/cpu0/cpuidle/state3/usage:68278
/sys/devices/system/cpu/cpu0/cpuidle/state3/time:114859261
While testing this, I discovered a side effect of nolapic_timer that has
bothered me for a while: Playing a sound has a program-specific probability of
putting the soundcard in what I would describe as "spark gap modulation mode",
which sounds freakin' awful. Restarting X always resets to normal mode. There
are at least 2 severities of spark gap modulation, depending on which, normal
mode can also be restored by playing a sound in Amarok using the Xine backend.
Playing a sound in Audacity has a 100% probability of invoking spark gap
modulation.
BIOS news:
My bios is version 1.16. The newest is 1.18. The changelogs list only 2 changes
from 1.16 (se my previous post or below).
Multicom says:
* The changes listed for IFT also applies to JFT models like mine.
* Bios upgrading is done at my own risk (may brick the motherboard).
* Upgrading is recommended (without indication to whether it helps).
I followed the guide at http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90,
but FreeDOS failed to install itself to my 1GB USB stick for no apparent
reason. Since I don't see how "Fix ICH8M B2 S3 resume failure" or "Update UCODE
for Merom CPU" is going to fix hpet, I won't try any harder. Also, I depend on
this computer, so I'm afraid my merge window is closed until summer.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.