http://bugzilla.novell.com/show_bug.cgi?id=527800
User pgnet.dev@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=527800#c5
--- Comment #5 from pgnet Dev
cpu MHz : 4294967.294
are certainly odd (and wrong).
agreed.
As to xenpm functionality - I'm not even sure it's properly wired up for AMD in -unstable. But even if it is, the changes are too extensive to be considered for a backport.
understood. unfortunate, but ... checking @ http://www.suse.de/~coolo/factory-status.html, Name Devel Project Maintainer Failing Requests Version Upstream Comment .. xen Virtualization charlesa 2 d Project.diff in devel project 3.4.1_19711_01 3.4.0 python moved .. the *xen version* is @ least new enough. reading @ http://wiki.xensource.com/xenwiki/xenpm, "the default governor is userspace governor. Xen also supports three CPU drivers: ACPI (IA32) for Intel x86 processor; ACPI (IA64) for Intel Itanium processor and PowerNow K8 for AMD processor." seems to imply AMD *is* supported. however, if the wiring you're referring to is that "in *suse", then i've no clue ... nonetheless, important to have, i'd suggest.
So bottom line is, all originally brought up issues are unlikely to be fixed,
ok, so we have to live with defaults for now. given that, per xen wiki (for which version applicable, who knows?), "The default is the hypervisor based cpufreq", I rm'd "cpufreq=xen" from the grub boot line ... expecting that behavior, from above, should not change. BUT, cat /proc/cpuinfo | egrep -i "proc|mhz" processor : 0 model name : AMD Phenom(tm) II X4 920 Processor cpu MHz : 2800.080 power management: ts ttp tm stc 100mhzsteps hwpstate processor : 1 model name : AMD Phenom(tm) II X4 920 Processor cpu MHz : 2800.080 power management: ts ttp tm stc 100mhzsteps hwpstate processor : 2 model name : AMD Phenom(tm) II X4 920 Processor cpu MHz : 2800.080 power management: ts ttp tm stc 100mhzsteps hwpstate processor : 3 model name : AMD Phenom(tm) II X4 920 Processor cpu MHz : 2800.080 power management: ts ttp tm stc 100mhzsteps hwpstate shows that it does. and, xenpm get-scaling-governor Xen cpuidle is not enabled! Xen cpufreq is not enabled! so, are we 'back' to vanilla, non-xen Dom0 pm? apparently not, cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to http://bugs.opensuse.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU analyzing CPU 1: no or unknown cpufreq driver is active on this CPU analyzing CPU 2: no or unknown cpufreq driver is active on this CPU analyzing CPU 3: no or unknown cpufreq driver is active on this CPU so is, or isn't, opensuse-xen's cpufreq=xen active as a/the default? at the very least, i'd suggest that whatever state the default is should not appear broken ...
only this last issue is something we ought to look into.
happy to provide whatinfo i can ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.