From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Stop the continuous flood of (XEN) traps.c:2432:d0
 Domain attempted WRMSR ..
Date: Fri, 3 Feb 2012 13:55:27 -0500
Message-ID: <20120203185527.GA9290@phenom.dumpdata.com>
References: <20120203180952.GP12984@reaktio.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <20120203180952.GP12984@reaktio.net>
List-Unsubscribe: <http://lists.xensource.com/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Fri, Feb 03, 2012 at 08:09:52PM +0200, Pasi K=E4rkk=E4inen wrote:
> Hello,
> =

> IIRC there was some discussion earlier about these messages in Xen's dmes=
g:
> =

> (XEN) traps.c:2432:d0 Domain attempted WRMSR 00000000000001ac from 0x0000=
000000c800c8 to 0x0000000080c880c8.
> (XEN) traps.c:2432:d0 Domain attempted WRMSR 00000000000001ac from 0x0000=
000000c800c8 to 0x0000000080c880c8.
> (XEN) traps.c:2432:d0 Domain attempted WRMSR 00000000000001ac from 0x0000=
000000c800c8 to 0x0000000080c880c8.
> (XEN) traps.c:2432:d0 Domain attempted WRMSR 00000000000001ac from 0x0000=
000000c800c8 to 0x0000000080c880c8.
> =

> At least on my systems there's continuous flood of those messages, so the=
y 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=3D470035,
> 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