This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] 2.6.37 dom0 under Xen 4.1 clocksource not working

To: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] 2.6.37 dom0 under Xen 4.1 clocksource not working
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 26 Jan 2011 07:40:47 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 26 Jan 2011 07:41:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D2B206B.3010707@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D2B206B.3010707@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7
On 01/10/2011 07:06 AM, Daniel De Graaf wrote:
> When booting 2.6.37 (from kernel.org) under Xen 4.1, there are
> apparently issues with timer interrupts being delivered to the dom0.
> Repeatedly causing an interrupt (for example, the ACPI power button) will
> allow the system to boot, as does adding "clocksource=jiffies" to the
> kernel command line. This is only present under Xen, not when booting the
> same kernel on real hardware.

Ah, yes.  This is from the cpuidle stuff, I think.  Does booting with
"idle=halt" work?

> When boot with clocksource=jiffies, the system will sometimes freeze
> for about 30 seconds and then continue; however, this could be related
> to kernel debugging that I have enabled.
> The only clock-related message in dmesg is:
> [  153.483813] Clocksource tsc unstable (delta = -77312555973 ns)
> /sys/devices/system/clocksource/clocksource0/available_clocksource:
>   xen jiffies tsc
> I can attach kernel config or other information as required. I have
> observed this on at least two platforms; the 2.6.32.x xen kernels do not
> exhibit this behavior.


Xen-devel mailing list