AW: Re: [Xen-devel] No C-States any longer...

["Carsten Schiers" <carsten@xxxxxxxxxx>]

Sorry, wanted to emphasize on the following anomalies:

xm dmesg:

(XEN) traps.c:2375:d0 Domain attempted WRMSR 00000000c0010004 from 
0x00007676727ffab2 to 0x0000000000000000.
(XEN) traps.c:2375:d0 Domain attempted WRMSR 00000000c0010000 from 
0x00000301181cccaf to 0x0000000000430076.
(XEN) traps.c:2375:d0 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d0 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d0 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d1 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d2 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d4 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d5 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d6 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d7 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d8 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d8 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d9 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d10 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.
(XEN) traps.c:2375:d10 Domain attempted WRMSR 00000000c0010048 from 
0x0000000000780000 to 0x0000000000780400.

dmesg Dom0:

[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 2, version 0, address 0xfec00000, GSI 
0-0
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ERROR: Unable to locate IOAPIC for GSI 2
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high 
level)
[    0.000000] ERROR: Unable to locate IOAPIC for GSI 9
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high 
edge)
[    0.000000] ERROR: Unable to locate IOAPIC for GSI 14
[    0.000000] Using ACPI (MADT) for SMP configuration information
...
[    0.008500] ------------[ cut here ]------------
[    0.008575] WARNING: at arch/x86/xen/enlighten.c:729 
init_hw_perf_events+0x337/0x3d7()
[    0.008674] Hardware name: M56S-S3
[    0.008741] Modules linked in:
[    0.008848] Pid: 0, comm: swapper Not tainted 2.6.32.40-xen-amd64 #2
[    0.008922] Call Trace:
[    0.008993]  [<ffffffff8104d73f>] ? warn_slowpath_common+0x76/0x8c
[    0.009071]  [<ffffffff814e1113>] ? init_hw_perf_events+0x337/0x3d7
[    0.009148]  [<ffffffff814e0c20>] ? identify_boot_cpu+0x15/0x3d
[    0.009223]  [<ffffffff814e0db7>] ? check_bugs+0x9/0x2e
[    0.009297]  [<ffffffff814d9ce3>] ? start_kernel+0x3cb/0x3e5
[    0.009371]  [<ffffffff814dbb4e>] ? xen_start_kernel+0x5ae/0x5b4
[    0.009450] ---[ end trace a7919e7f17c0a725 ]---
...
[    0.049594] ERROR: Unable to locate IOAPIC for GSI 9
...

BR,
Carsten.



-----Ursprüngliche Nachricht-----
Von: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx] 
Gesendet: Montag, 6. Juni 2011 10:31
An: Carsten Schiers
Cc: xen-devel
Betreff: Re: [Xen-devel] No C-States any longer...

On Sat, 2011-06-04 at 17:18 +0100, Carsten Schiers wrote:
> after my move to Xen 4.1.0 and Debian 2.6.32-5-xen-amd64 pvops Dom0. 
> Seems to be a problem with ACPI.
> Can it be a BIOS problem (although it worked up to now) or is this not 

> implemented? 

It may not have been implemented when Debian took their snapshot of
pvops for the Squeeze release or there may have been missing bugfixes.
Can you try the latest xen.git#xen/stable-2.6.32?

> Some infos:

It might be interesting to see the equivalent on a working system. Also
a complete dmesg from each case would be useful.

Ian.

> 
> xm dmesg after xm debug-key c:
> --------------------------------
> (XEN) 'c' pressed -> printing ACPI Cx structures
> 
> xenpm get-cpuidle-states 0
> --------------------------
> Max C-state: C7
> 
> cpu id               : 0
> total C-states       : 0
> idle time(ms)        : 0
> pc3                  : [00000000000000000018 ms]
> pc6                  : [00000000000000004294 ms]
> pc7                  : [00000000000140733193 ms]
> cc3                  : [00000000000000000000 ms]
> cc6                  : [00000000000000000006 ms]
> 
> xm info
> -------
> host                   : data
> release                : 2.6.32-5-xen-amd64
> version                : #1 SMP Thu May 19 01:16:47 UTC 2011
> machine                : x86_64
> nr_cpus                : 3
> nr_nodes               : 1
> cores_per_socket       : 3
> threads_per_core       : 1
> cpu_mhz                : 2210
> hw_caps                : 
> 
178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000
> virt_caps              : hvm
> total_memory           : 4094
> free_memory            : 373
> free_cpus              : 0
> xen_major              : 4
> xen_minor              : 1
> xen_extra              : .0
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 

> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : unavailable
> xen_commandline        : dom0_mem=256M dom0_vcpus_pin cpuidle 
> cpufreq=xen
> cc_compiler            : gcc version 4.4.5 (Debian 4.4.5-8)
> cc_compile_by          : root
> cc_compile_domain      :
> cc_compile_date        : Fri Jun  3 17:03:43 CEST 2011
> xend_config_format     : 4
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel





_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel