https://bugzilla.novell.com/show_bug.cgi?id=436717
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c7
Thomas Renninger changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joachim.deguara@amd.com
Status|ASSIGNED |NEEDINFO
Info Provider| |mdrolc@gmail.com
--- Comment #7 from Thomas Renninger 2008-12-23 09:20:45 MST ---
You can watch/monitor cpufreq easily on command-line:
watch -n1 cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_{cur_freq,max_freq}
Then you have the current and maximum allowed frequency shown every second.
This is a BIOS issue or say a OS communication problem with the BIOS.
Best:
attach acpidump output.
Then search and eventually update to the latest BIOS.
Then again attach acpidump output.
If this still happens then, there are generally 2 possibilities why/how BIOS is
setting this:
- passive cooling (passive trip-point exceeded), do:
watch -n1 cat /proc/acpi/thermal_zone/THRM/{temperature,trip_points}
You there see the current temperature and eventually a passive trip point.
If the passive trip point is exceeded, the OS starts to lower the max_freq
value. Please attach/paste output of:
cat /proc/acpi/thermal_zone/THRM/{temperature,trip_points}
- _PPC tell the OS which frequencies are allowed to be used.
Try boot param: processor.ignore_ppc=1
Double check whether the parameter really got set:
cat /sys/module/processor/parameters/ignore_ppc
Does it work now? Is:
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
set to the real max now?
This bug has made it into 11.1 GM
Hey guys, I set the prio to 1, this is the maximum I can set it to.
There was no answer for a month.
I really like to find the root cause, if you also do and you are willing to
invest a bit of time, let's track this one down in the next year. An update
kernel for 11.1 should pop up pretty soon. Thanks.
--
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.