'powernow-k8 transition frequency failed'에 해당되는 글 1건

  1. 2012.04.02 powernow-k8 transition frequency failed
Linux/Ubuntu2012.04.02 22:51
Ubuntu 11.10 Desktop 64bit 에서 발생하고 있고 AMD 4200+x2 이다.
대충 찾아봐도 Cool'n'Quiet 관련해서 문제라는 이야기가 있는데
내가 그걸 안켜놨던가...?

Motorola | A853 | Normal program | Center-weighted average | 1/15sec | F/2.8 | 0.00 EV | 4.0mm | ISO-199 | Off Compulsory | 2012:04:02 22:19:14

2012.4.3 추가

위의 에러는 ACPI 관련해서 문제가 발생하는 것으로 Cool'n'Quiet를 켜놓으면 발생한다고 한다.

On AMD with Xen, the cpuidle is set to use the halt one (this is b/c the halt
ends up doing a yield hypercall) - look in setup.c - and the hypervisor does
the appropiate halt operation (MWAIT, halt, etc, or schedules another guest on
the CPU). Anyhow, to not have the cpuidle trying to activate, the
"boot_option_idle_override" is set. Therefore, the ACPI _PSS driver
(processor.ko) ends up bailing out, b/c of that parameter. As such the "older"
AMD pstate driver is invoked (powernow-k8), and the older driver attempts to
use ACPI _PSD - but only if in UP mode, or it attempts to use the voltage
tables - which are k8 or earlier. To detect that, it use the MSR (sadly not
CPUID values), which Xen traps and returns 00, which the powernow-k8 driver
interprets as "buggy hardware - can't use". Which is exactly what you are

I believe (and sadly I don't have the hardware to check this - but I think I
saw the somebody using it) if you were running on K8 hardware - it ought to

Solution: Have the ACPI processor driver cooperate with Xen. Patches are in the
queue for it (if you are really interested look in oss.oracle.com/kwilk/xen.git
#devel/acpi-cpufreq.v2 - but they are not yet upstream-able material. Actually,
they are quite ugly).

Other solution:
The "easy" option for right now would be to do what Dave suggest until the
upstream patches are ready and reviewed.
Just to add, per Konrad's comment above.

This issue also occurs on K8 hardware (Athlon II 4850e) with powernow enabled
in the BIOS (aka Cool'n'quiet).

Disabling Cool'n'quiet removes the messages.

I just performed the standard Desktop install of the F16 Beta, installed Xen,
rebuilt the grub menu, and rebooted to dom0.  Syslog is full of the same
message per this bug.

It would be great to see Dave's solution (see comment 5 above); an interim
kernel-patch solution to this bug - as it currently stands dom0 functionality
is largely unuseable.
[링크 : https://bugzilla.redhat.com/show_bug.cgi?id=739159]  
2012.4.4 추가
확실히 Cool'n'Quiet를 끄니 에러가 발생하진 않음.

Posted by 구차니

댓글을 달아 주세요