https://bugzilla.novell.com/show_bug.cgi?id=299891#c57
Thomas Renninger changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hmacht@novell.com
--- Comment #57 from Thomas Renninger 2007-09-25 07:13:25 MST ---
I put a cpufreq debug enabled kernel here:
ftp.suse.com/pub/people/trenn/cpufreq_debug_10_3/kernel-default-2.6.22.7-31.x86_64.rpm
Can you install that one pls.
Next we should make sure the cpufreq modules can be loaded manually (even with
passing CPUFREQ=off, AFAIK only hal start script is looking out for this):
Boot the newly installed kernel with CPUFREQ=off and cpufreq.debug=7
modprobe processor (might already be loaded)
modprobe powernow-k8
modprobe cpufreq_ondemand
echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ondemand >/sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo ondemand >/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo ondemand >/sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
Now the machine should switch off. You should be able to extract extra cpufreq
related debug info from /var/log/messages (from last boot).
If it does not switch off, it possibly might be some strange interference
between ACPI modules and cpufreq and we need to dig further.
As said, you might want to contact me via ICQ, I can help then interactively
that might speed up things...
--
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.