[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Stop the continuous flood of (XEN) traps.c:2432:d0 Domain attempted WRMSR ..



On Fri, Feb 03, 2012 at 08:09:52PM +0200, Pasi Kärkkäinen wrote:
> Hello,
> 
> IIRC there was some discussion earlier about these messages in Xen's dmesg:
> 
> (XEN) traps.c:2432:d0 Domain attempted WRMSR 00000000000001ac from 
> 0x0000000000c800c8 to 0x0000000080c880c8.
> (XEN) traps.c:2432:d0 Domain attempted WRMSR 00000000000001ac from 
> 0x0000000000c800c8 to 0x0000000080c880c8.
> (XEN) traps.c:2432:d0 Domain attempted WRMSR 00000000000001ac from 
> 0x0000000000c800c8 to 0x0000000080c880c8.
> (XEN) traps.c:2432:d0 Domain attempted WRMSR 00000000000001ac from 
> 0x0000000000c800c8 to 0x0000000080c880c8.
> 
> At least on my systems there's continuous flood of those messages, so they 
> will fill up the
> Xen dmesg log buffer and "xm dmesg" or "xl dmesg" won't show any valuable 
> information, just those messages.

Is it always that MSR? That looks to be TURBO_POWER_CURRENT_LIMIT
which is the intel_ips driver doing.

> 
> I seem to be getting those messages even when there's only dom0 running.
> Is the plan to drop those messages? What's causing them? 

Looks to be the intel-ips. If you rename it does the issue disappear?
> 
> hmm, according to this bugzilla 
> https://bugzilla.redhat.com/show_bug.cgi?id=470035,
> they're related to dom0 kernel acpi-cpufreq ?
> 
> Also it seems there was discussion about the subject on 2011/08:
> http://old-list-archives.xen.org/archives/html/xen-devel/2011-08/msg00561.html
> 
> 
> Xen hypervisor 4.1.2.
> dom0 Linux kernel 3.2.2.
> 
> 
> Thanks,
> 
> -- Pasi

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.