WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen unstable crash

To: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Subject: Re: [Xen-devel] Xen unstable crash
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 17 Mar 2009 11:43:30 +0000
Cc: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 17 Mar 2009 04:44:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f4527be0903170337s5fb0570ayd9e733bc5f5430eb@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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acmm7FL6p6osITpQT5ihEFgpEaJSUQACUTFz
Thread-topic: [Xen-devel] Xen unstable crash
User-agent: Microsoft-Entourage/12.15.0.081119
On 17/03/2009 10:37, "Andrew Lyon" <andrew.lyon@xxxxxxxxx> wrote:

>> Building now... I noticed that both of those changesets touch multi.c,
>> and I happened to notice this message was displayed before one of the
>> crashes:
>> 
>> (XEN) multi.c:3348:d12 write to pagetable during event injection:
>> cr2=0x80392d74, mfn=0xb58bb
>> 
> Reverting those two changesets did not stop the problem, I didn't get
> the crash message this time because the scrollback buffer in my serial
> console had been overwritten before I got a change to copy it, but it
> looked the same as the others.

Hmm.. I'll have to draw up a new hit list of suspicious changesets. The
difficulty of bisecting a problem when we have two separate repositories
uinvolved (xen-unsatble and the qemu repo) is something we may have to
consider after 3.4 is out. It's worked okay so far but it does rather break
down when the bugs hit the fan!

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel