From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: 2.6.37 dom0 under Xen 4.1 clocksource not working
Date: Tue, 11 Jan 2011 10:26:22 -0500 [thread overview]
Message-ID: <20110111152622.GC10897@dumpdata.com> (raw)
In-Reply-To: <4D2B206B.3010707@tycho.nsa.gov>
On Mon, Jan 10, 2011 at 10:06:19AM -0500, 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.
>
> 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)
I see it too.
>
> /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.
I think we are just missing some of the Xen time code that is in 2.6.32
but has not been ported over to 2.6.37. I don't remember the name of the
patches thought..
next prev parent reply other threads:[~2011-01-11 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 15:06 2.6.37 dom0 under Xen 4.1 clocksource not working Daniel De Graaf
2011-01-11 15:26 ` Konrad Rzeszutek Wilk [this message]
2011-01-26 15:40 ` Jeremy Fitzhardinge
2011-01-26 16:11 ` Daniel De Graaf
2011-01-26 17:07 ` Stefano Stabellini
2011-01-26 20:12 ` Konrad Rzeszutek Wilk
2011-01-27 1:18 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110111152622.GC10897@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.