From: Jens Seidel <jensseidel@users.sf.net>
To: linux-kernel@vger.kernel.org
Subject: CE: xen increasing min_delta_ns to 7651397591976463850 nsec
Date: Mon, 22 Feb 2010 09:26:59 +0100 [thread overview]
Message-ID: <20100222082657.GA26436@merkur.sol.de> (raw)
Hi,
I'm using vanilla 2.6.32.7 domU kernel with Xen 3.2 and get very often a
unresponsible system after approximately one or two days with messages such as
[43616.674502] CE: xen increasing min_delta_ns to 16086592372704132408 nsec
[43616.674502] CE: xen increasing min_delta_ns to 5683144485346646996 nsec
[43616.674502] CE: xen increasing min_delta_ns to 17748088764874746302 nsec
[43616.674502] CE: xen increasing min_delta_ns to 17398761110457343644 nsec
[43616.674502] CE: xen increasing min_delta_ns to 7651397591976463850 nsec
[43616.674502] CE: xen increasing min_delta_ns to 2253724351109919966 nsec
[43616.674502] CE: xen increasing min_delta_ns to 3380586526664879948 nsec
[43616.674502] CE: xen increasing min_delta_ns to 5070879789997319922 nsec
[43616.674502] CE: xen increasing min_delta_ns to 7606319684995979882 nsec
[43616.674502] CE: xen increasing min_delta_ns to 11409479527493969822 nsec
[43616.674502] CE: xen increasing min_delta_ns to 17114219291240954732 nsec
on the console. I fail to login via ssh and even to cleanly shutdown this
system via xm <id> shutdown. sysrq requests still work.
I searched the net but found only messages with 15000 nsec. My values are a
little bit larger :-)) Found references to the kernel parameter notsc and
tried it but the problem remains.
The problem started once I upgraded the kernel from 2.6.26 to 2.6.32.7.
I changed from 32bit to 64bit but apart from this I did only a make oldconfig.
That's why I think it's not my config which causes trouble.
Any ideas? Is it a known problem?
PS: Please CC: me.
Jens
next reply other threads:[~2010-02-22 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 8:26 Jens Seidel [this message]
2010-02-25 21:44 ` CE: xen increasing min_delta_ns to 7651397591976463850 nsec / pvops domU Pasi Kärkkäinen
2010-02-25 22:33 ` Jens Seidel
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=20100222082657.GA26436@merkur.sol.de \
--to=jensseidel@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
/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