https://bugzilla.novell.com/show_bug.cgi?id=299891#c52
Thomas Renninger changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark.langsdorf@amd.com, Ulrich.Windl@rz.uni-
| |regensburg.de, joachim.deguara@amd.com
--- Comment #52 from Thomas Renninger 2007-09-24 09:18:30 MST ---
#comment 32 states that the processor module could not be loaded (therefore
powernow-k8 could not be loaded which needs the processor module). I expect,
there a boot param like acpi=off has been used accidently.
About comment #42: The problem is that our userspace acpica sources are
*really* old and the problem I mentioned in that comment should already be
fixed. But Intel has not published the fixed sources, we still have to use the
code from more than a year ago which makes this one very hard to debug (-> Len,
we have to talk about this again privately, I hope there wasn't some kind of
policy change at Intel about this...).
Bug #297119 has a very similar CPUFreq states declaration: Declares a package
of size 2. In it there are 2 valid packages and 4 invalid (0xFFFFF...)
packages, the latter ones have to be ignored totally. There the invalid
packages are exported to cpufreq layer (!ACPI bug!) and the powernow-k8 module
seem to have a sanity check on the exported values and ignores them: invalid
freq entries 3900000 kHz vs. 65535000 kHz.
It's too late now to fix the ACPI parse now, I try to find a sanity check for
powernow-k8:
There is a differenciation depending on a processor capability flag, the
variable used is cpu_family and can be CPU_OPTERON and CPU_HW_PSTATE. In bug
297119 we have a non Opteron, here it is a Opteron and I expect therefore:
fill_powernow_table_pstate (-> non-opteron case)
and
fill_powernow_table_fidvid (-> operon case)
is used to initialise and sanity check these values.
The non-opteron case looks more scary (a read msr is done with the bogus
info)... Anyway, better ignore all bogus info and mark it invalid at the very
beginning.
If it's this, attached patch should help and should be safe enough to go in,
even for RCx.
I built an rpm for you to test, verification whether everything is fine now
would be appreciated (it may take some hours until the ftp server got synced
and the file pops up):
ftp.suse.com/pub/people/trenn/wrong_acpi_freq_info/kernel-default-2.6.22.5-29.x86_64.rpm
--
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.