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] New release candidate for Xen 4.0.0 (RC9)

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] New release candidate for Xen 4.0.0 (RC9)
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 31 Mar 2010 17:07:16 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 31 Mar 2010 14:08:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7D96A13.EDA7%keir.fraser@xxxxxxxxxxxxx>
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>
References: <20100331195223.GA15322@xxxxxxxxxxxxxxxxxxx> <C7D96A13.EDA7%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Wed, Mar 31, 2010 at 09:07:31PM +0100, Keir Fraser wrote:
> On 31/03/2010 20:52, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:
> 
> >>> I don't have a fix, but I did this (this is with xen/stable-2.6.32.x
> >>> latest and also rolled back to git commit
> >>> 47bd9cad11b1a723c6e5d1127aebe570a3e34f34
> >>> with a cherry pick of d3b9e35a81e31ff4edb4666f9c36eb5b2032f4da - just in
> >>> case
> >>> the problem was due to the PAT changes):
> >> 
> >> Is it a regression?
> > 
> > I haven't tried this type of operation before so I can't comment. I can
> > spin out a Xen hypervisor - what version back do you want me to compare
> > to?
> 
> Last stable release (3.4.2). Or even 3.4-testing tip.
> 
> I'm only interested in fixing regressions right now for 4.0.0. If this bug
> has existed since at least 3.4 then the fix (when we have one!) can wait a
> bit longer, for 4.0.1. My guess is that the MTRR interface is getting little

Yeah. I get the same failure with 3.4 from xen-3.4-testing:


echo "disable=2" > /proc/mtrr
(XEN) Assertion '((lock)->lock <= 0)' failed at 
/home/konrad/git/tip/nex-VI/xen/xen/include/asm/sp:18
(XEN) ----[ Xen-3.4-100331000000000000000f   rdi: ffff828c8020ce20
(XEN) rbp: ffff828c8026fcb8   rsp: ffff828c8026fcb8   r8:  ffff828c8026fc68
(XEN) r9:  ffff828c8026fc60   r10: 0000000000000000   r11: 00000000f0000800
(XEN) r12: 0000000000000000   r13: 0000000000000002   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000006f0
(XEN) cr3: 00000000cad0e000   cr2: 00007fe07ea35385
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff828c8026fcb8:
(XEN)    ffff828c8026fcc8 ffff828c80184265 ffff828c8026fd08 ffff828c801843d7
(XEN)    0000000000000086 ffff828c8026fd28 0000000000000002 0000000000000246
(XEN)    ffff828c8026fd2c 80000000bd4d7165 0000000000000000 0000000000000002
(XEN)    ffff8800bf5efc80 80100000be263065 0000000800000000 0000000000000000
(XEN)    00000000000be263 ffff820000000002 0000000000000006 0000000000000002
(XEN)    0000000000000008 0000000000000002 0000000000000000 0000000000000000
(XEN)    ffff828c8026fde8 ffff828c80184a19 0000000000000000 ffff8300cfada000
(XEN)    0000000000000000 0000000000000001 0000000000010000 00000000000c0000
(XEN)    06ff828c80140877 fffffffffffffff3 ffff880007dcade8 ffff8800062f5d6c
(XEN)    00000000000004fd 0000000000000000 ffff828c8026ff08 ffff828c801428e3
(XEN)    0000000000000000 0000000000000001 0000000000000282 ffff828c8026fe40
(XEN)    ffff8300cfada000 ffff8300cfcce000 0000002b4d860d0b 0000000000000001
(XEN)    ffff828c80244100 ffff828c8026fec0 0300000100000020 0000000200000000
(XEN)    0000002b17ecba31 0000002ac27e0b7b ffff880007ddce40 ffff880007ddce40
(XEN)    0000000000000000 ffff880007dd2020 ffff880007dcae38 ffffffff810117da
(XEN)    ffff880007dcae88 ffffffff81011a80 0000000000000000 0000002b4d860d0b
(XEN)    00000002afcbb5c2 000000000167cfd4 000000287eb6586a ffff828c8026ff28
(XEN)    ffff828c80244d30 ffff8300cfada000 00000000ffff00ff ffff8800062f5d6c
(XEN)    00000000000004fd 0000000000000000 00007d737fd900b7 ffff828c801d61dc
(XEN)    ffffffff810090ea 0000000000000007 0000000000000000 00000000000004fd
(XEN) Xen call trace:
(XEN)    [<ffff828c8011bd14>] _spin_unlock+0xc/0x22
(XEN)    [<ffff828c80184265>] post_set+0x70/0x72
(XEN)    [<ffff828c801843d7>] generic_set_mtrr+0xd9/0xf3
(XEN)    [<0000000000000002>] ???
(XEN)    
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion '((lock)->lock <= 0)' failed at 
/home/konrad/git/tip/nex-VI/xen/xen/include/asm/sp:18
(XEN) ****************************************
(XEN) 

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