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] 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 15:10:19 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 31 Mar 2010 12:11:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7D8D409.F531%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: <C7D8D409.F531%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Wed, Mar 31, 2010 at 10:27:21AM +0100, Keir Fraser wrote:
> Folks,
> 4.0.0-rc9 is now tagged in http://xenbits.xensource.com/xen-4.0-testing.hg
> This is almost certainly the last RC, and will become the 4.0.0 release
> around the middle of next week. Please test!

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 
with a cherry pick of d3b9e35a81e31ff4edb4666f9c36eb5b2032f4da - just in case
the problem was due to the PAT changes):

-sh-3.1# cat /proc/mtrr
reg00: base=0x000000000 (    0MB), size= 2048MB, count=1: write-back
reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
reg02: base=0x0c0000000 ( 3072MB), size=  256MB, count=1: write-back
-sh-3.1# echo "disable=2" > /proc/mtrr
(XEN) Assertion '((lock)->lock <= 0)' failed at 
(XEN) ----[ Xen-4.1-100331c50   rcx: 00000000000006f0
(XEN) rdx: ffff82c480278a18   rsi: 000000000000000f   rdi: ffff82c480244ee0
(XEN) rbp: ffff82c48037fc98   rsp: ffff82c48037fc98   r8:  ffff82c48037fc48
(XEN) r9:  ffff82c48037fc40   r10: 0000000000000002   r11: 0000ffff0000ffff
(XEN) r12: 0000000000000000   r13: 0000000000000002   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000006f0
(XEN) cr3: 00000002245d3000   cr2: 00007f5c26627b78
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff82c48037fc98:
(XEN)    ffff82c48037fca8 ffff82c48019cce5 ffff82c48037fce8 ffff82c48019ce57
(XEN)    0000000000000086 ffff82c48037fd08 0000000000000002 0000000000000246
(XEN)    0000000000000000 ffff82c48037fd0c ffff82c48037fd58 ffff82c48019d24b
(XEN)    0000000000218129 ffff82c480170eee ffff82c48037fd18 ffff82c480170fe7
(XEN)    ffff83022fee0000 000000028011f675 0000000000000002 ffff8300cfee8000
(XEN)    ffff83022fee0000 0000000000000002 0000000000000000 ffff880008130020
(XEN)    ffff82c48037fdc8 ffff82c48019d525 0000000000000008 ffff82c48037fdb0
(XEN)    0000000000000000 ffff82c48027e080 0000000000010000 00000000000c0000
(XEN)    06ff8300cfdbe000 fffffffffffffff3 ffff880008128df8 ffff880008128df8
(XEN)    0000000000000000 ffff880008130020 ffff82c48037ff08 ffff82c480153fc3
(XEN)    0000000000006000 0000000000000056 ffff82c48037fe00 ffff82c48037fe30
(XEN)    ffff82c4801746d4 0000000000000001 0000000000000000 ffff82c48037fe40
(XEN)    ffff8300cfee8000 ffff8300cfdbe000 00000015a25fa88c 0000000000000001
(XEN)    ffff82c480278080 ffff82c48037fec0 0300000100000020 0000000200000000
(XEN)    ffff880008139d00 ffff880008139d00 0000000000000000 ffff880008130020
(XEN)    ffff880008128e38 ffffffff810115c6 ffff880008128e88 ffffffff8101186c
(XEN)    0000000000000000 00000015a25fa88c 0000000218c6f130 0000000002753c6a
(XEN)    00000012ba64a0c1 00000000c3b44ffa 0000000000000000 ffff82c48037ff28
(XEN)    ffff82c480279280 ffff8300cfee8000 00000000ffff00ff ffff880006aebd6c
(XEN)    0000000000000000 ffff880008130020 00007d3b7fc800b7 ffff82c4801fb1dc
(XEN) Xen call trace:
(XEN)    [<ffff82c48011fa40>] _spin_unlock+0xc/0x22
(XEN)    [<ffff82c48019cce5>] post_set+0x70/0x72
(XEN)    [<ffff82c48019ce57>] generic_set_mtrr+0xd9/0xf3
(XEN)    [<ffff82c48019d24b>] set_mtrr+0xda/0x121
(XEN)    [<ffff82c48019d525>] mtrr_del_page+0x172/0x199
(XEN)    [<ffff82c480153fc3>] do_platform_op+0x283/0x1af8
(XEN)    [<ffff82c4801fb1dc>] syscall_enter+0x10c/0x166
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion '((lock)->lock <= 0)' failed at 
(XEN) ****************************************

I tested the same exact kernel on baremetal, and had no trouble with the
above mentioned command. The machine is a Dell T105 AMD 1352 w/ 8GB of

Xen-devel mailing list