This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Hunting down an oops in Xen 3.1.0's 2.6.18 kernel

To: Michael Marineau <mike@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Hunting down an oops in Xen 3.1.0's 2.6.18 kernel
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 15 Sep 2007 08:07:34 +0100
Delivery-date: Sat, 15 Sep 2007 00:03:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <c0526ddf0709141551x29edd2b6j85dd740ebd8cf929@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acf3ZxbTVT2wPGNaEdyNxwAWy6hiGQ==
Thread-topic: [Xen-devel] Hunting down an oops in Xen 3.1.0's 2.6.18 kernel
User-agent: Microsoft-Entourage/
On 14/9/07 23:51, "Michael Marineau" <mike@xxxxxxxxxxxx> wrote:

> I have been unable to reproduce this with 3.0.4's 2.6.16 kernel but
> 2.6.18 will oops on both 3.0.4 and 3.1.0. Also, x86_64 appears to be
> ok.
> I'm guessing this issue is the same as the oops reported here:
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=975
> Below is an example of the oops on my 2.6.18 pae kernel with a couple
> extra debuging lines added:

Looks like xen_l1_entry_update() is passed a virtual address which has no
corresponding machine address. So the pte page or its mapping is corrupted
somehow. deadbeef in the register dumps is also not a good sign. I'll have a
go at repro'ing.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>