From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark McLoughlin <markmc@redhat.com>
Subject: Re: 2.6.29-rc3 oops with kvmclock
Date: Tue, 03 Feb 2009 11:50:34 +0000
Message-ID: <1233661834.3726.25.camel@blaa>
References: <1233656727.3726.23.camel@blaa>
	 <5d6222a80902030230k39ade6b8lc87cae32ddbed5b3@mail.gmail.com>
Reply-To: Mark McLoughlin <markmc@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: kvm <kvm@vger.kernel.org>
To: Glauber Costa <glommer@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:42313 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751763AbZBCLul (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 3 Feb 2009 06:50:41 -0500
In-Reply-To: <5d6222a80902030230k39ade6b8lc87cae32ddbed5b3@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Tue, 2009-02-03 at 08:30 -0200, Glauber Costa wrote:
> On Tue, Feb 3, 2009 at 8:25 AM, Mark McLoughlin <markmc@redhat.com> wrote:
> > Hi,
> >
> > Same guest, this time a kvmclock related oops.
> 
> How do you know that? There is kvmclock related functions in the trace
> as could be
> any clock related function.

Yep, that's all I meant - "kvmclock is in the trace".

>  The problem smells like bad mmu to me at a first glance.

Sure.

Cheers,
Mark.