From: Bernhard Schmidt <berni@birkenwald.de>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: Clock jumps
Date: Thu, 27 May 2010 23:48:18 +0200 [thread overview]
Message-ID: <4BFEE8A2.30706@birkenwald.de> (raw)
In-Reply-To: <AANLkTindrSuRdOI30l4P5XMuUVv3j7Zso9fMi1xREb3A@mail.gmail.com>
On 27.05.2010 21:08, john stultz wrote:
Hi John,
> I'd be very interested in hearing more about the host side issue. So
> this happened with the same kernel that you were using before, with no
> trouble?
Correct.
> Could you also send dmesg output from this boot? And if you can find
> any older dmesg logs to compare with, send those too?
See http://users.birkenwald.de/~berni/temp/dmesg-lenny and
http://users.birkenwald.de/~berni/temp/dmesg-squeeze . Although running
on the same kernel binary the initrd changed greatly when upgrading, so
ordering/timing between those two is off.
Note that the dmesg output is captured right after boot. I think I
remember seeing a "TSC unstable" message pretty soon after boot, but I
might be mixing it up with my other AMD-based KVM server. I don't hold
normal (non-boot) logs that long, so I can't tell for sure.
If you need any more info feel free to contact me.
Bernhard
next prev parent reply other threads:[~2010-05-27 22:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 16:06 Clock jumps Orion Poplawski
2010-05-25 6:21 ` Gleb Natapov
2010-05-26 17:10 ` Orion Poplawski
2010-05-26 17:31 ` Alexander Graf
2010-05-26 17:50 ` Orion Poplawski
2010-05-26 22:55 ` Orion Poplawski
2010-05-27 18:32 ` Bernhard Schmidt
2010-05-27 18:32 ` Bernhard Schmidt
2010-05-27 19:08 ` john stultz
2010-05-27 21:48 ` Bernhard Schmidt [this message]
2010-05-28 0:00 ` john stultz
2010-05-28 0:33 ` Bernhard Schmidt
2010-05-28 0:46 ` john stultz
2010-05-28 0:49 ` Bernhard Schmidt
2010-05-27 21:53 ` Zachary Amsden
2010-05-27 22:12 ` Bernhard Schmidt
2010-05-27 22:20 ` Zachary Amsden
2010-05-27 22:22 ` Zachary Amsden
2010-06-02 22:54 ` Orion Poplawski
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=4BFEE8A2.30706@birkenwald.de \
--to=berni@birkenwald.de \
--cc=johnstul@us.ibm.com \
--cc=kvm@vger.kernel.org \
--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 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.