From: Tobias Geiger <tobias.geiger@vido.info>
To: xen-devel@lists.xensource.com
Subject: Re: A clocksource question
Date: Fri, 12 Mar 2010 12:42:27 +0100 [thread overview]
Message-ID: <201003121242.27713.tobias.geiger@vido.info> (raw)
Hi,
i think i have the same Dom0 Problems as Joanna.
My setup is:
Xen 4.0.0-rc3-pre with some GFX-Passthrough Patches (btw: works great!)
with "vtd=1 dom0_max_vcpus=6 iommu=pv" as cmdline for xen
Dom0 Kernel is currently 2.6.33 using rebased Opensuse xen-patches (xen-
patches-2.6.33-1)
I also get - a slightly different - hrtimer message , but only in my Dom0 (as i
have only Windows HVM as DomU)
"hrtimer: interrupt took 2951458 ns"
This message seems to appear when my DomU is booting.
"clocksource=jiffies" as Dom0-Parameter doesn't help.
"max_cstate=0" as xen Parameter doesn't seem to help either.
The Patch from http://lists.xensource.com/archives/html/xen-
devel/2010-03/msg00570.html doesn't seem to help.
My "Hiccups" occur - felt - "randomly", they take from 1 up to 5 seconds (not
messured, more felt) and the only thing moving on the screen during that is
the mouse pointer. If it weren't for the moving pointer one could think the
Maschine is completly frozen.
The "Hiccups" are ONLY in the Dom0, its even so that i can perfectly work in
the DomU, even when one of these long-term-hiccups occur.
That all just in case another "affected" system my help you in your analsysis
of this strange behaviour.
Tell me if i can help testing.
Greetings
Tobias
P.S.: Sorry for the non-threaded Follow-up, but i just subscribed to the
list...
next reply other threads:[~2010-03-12 11:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 11:42 Tobias Geiger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-09 10:47 A clocksource question Joanna Rutkowska
2010-03-09 10:50 ` Keir Fraser
2010-03-09 10:54 ` Joanna Rutkowska
2010-03-09 11:06 ` Joanna Rutkowska
2010-03-09 12:07 ` Pasi Kärkkäinen
2010-03-09 12:10 ` Joanna Rutkowska
2010-03-09 15:42 ` Konrad Rzeszutek Wilk
2010-03-09 23:36 ` Jeremy Fitzhardinge
2010-03-10 22:13 ` Joanna Rutkowska
2010-03-11 0:07 ` Dan Magenheimer
2010-03-11 0:15 ` Joanna Rutkowska
2010-03-11 0:21 ` Ian Pratt
2010-03-11 0:44 ` Dan Magenheimer
2010-03-12 0:34 ` Joanna Rutkowska
2010-03-11 0:52 ` Joanna Rutkowska
2010-03-11 1:06 ` Jeremy Fitzhardinge
2010-03-11 1:19 ` Joanna Rutkowska
2010-03-11 4:55 ` Jeremy Fitzhardinge
2010-03-11 10:49 ` Joanna Rutkowska
2010-03-12 0:27 ` Joanna Rutkowska
2010-03-12 0:49 ` Jeremy Fitzhardinge
2010-03-12 0:38 ` Joanna Rutkowska
2010-03-12 19:02 ` Joanna Rutkowska
2010-03-12 21:24 ` Jeremy Fitzhardinge
2010-03-12 21:56 ` Tobias Geiger
2010-03-12 22:02 ` Jeremy Fitzhardinge
2010-03-12 21:01 ` Joanna Rutkowska
2010-03-12 21:13 ` Joanna Rutkowska
2010-03-12 23:48 ` Jeremy Fitzhardinge
2010-03-13 9:58 ` Joanna Rutkowska
2010-03-13 19:30 ` Jeremy Fitzhardinge
2010-03-15 6:49 ` Tobias Geiger
2010-03-16 6:01 ` Joanna Rutkowska
2010-03-17 13:35 ` Tobias Geiger
2010-03-17 15:21 ` Joanna Rutkowska
2010-03-17 16:20 ` Jeremy Fitzhardinge
2010-03-17 17:05 ` Joanna Rutkowska
2010-03-17 17:21 ` Jeremy Fitzhardinge
2010-03-17 16:26 ` Dan Magenheimer
2010-03-12 22:56 ` Tobias Geiger
2010-03-11 7:47 ` Keir Fraser
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=201003121242.27713.tobias.geiger@vido.info \
--to=tobias.geiger@vido.info \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).