From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: New release candidate for Xen 4.0.0 (RC9)
Date: Wed, 31 Mar 2010 15:10:19 -0400 [thread overview]
Message-ID: <20100331191019.GA18721@phenom.dumpdata.com> (raw)
In-Reply-To: <C7D8D409.F531%keir.fraser@eu.citrix.com>
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 47bd9cad11b1a723c6e5d1127aebe570a3e34f34
with a cherry pick of d3b9e35a81e31ff4edb4666f9c36eb5b2032f4da - just in case
the problem was due to the PAT changes):
-sh-3.1#
-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#
-sh-3.1# 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-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)
(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)
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
RAM.
next prev parent reply other threads:[~2010-03-31 19:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:27 New release candidate for Xen 4.0.0 (RC9) Keir Fraser
2010-03-31 10:07 ` Joanna Rutkowska
2010-03-31 10:54 ` Keir Fraser
2010-03-31 11:00 ` Joanna Rutkowska
2010-03-31 11:13 ` Keir Fraser
2010-03-31 12:38 ` Ian Pratt
2010-03-31 14:20 ` Dan Magenheimer
2010-03-31 14:32 ` Keir Fraser
2010-03-31 14:44 ` Ian Pratt
2010-03-31 19:55 ` Grant McWilliams
2010-03-31 15:02 ` Bastian Blank
2010-03-31 15:09 ` Keir Fraser
2010-03-31 15:44 ` Bastian Blank
2010-03-31 16:38 ` Keir Fraser
2010-03-31 18:03 ` Konrad Rzeszutek Wilk
2010-03-31 18:18 ` Keir Fraser
2010-03-31 20:40 ` Jeremy Fitzhardinge
2010-03-31 19:10 ` Konrad Rzeszutek Wilk [this message]
2010-03-31 19:33 ` Keir Fraser
2010-03-31 19:52 ` Konrad Rzeszutek Wilk
2010-03-31 20:07 ` Keir Fraser
2010-03-31 21:07 ` Konrad Rzeszutek Wilk
2010-05-19 12:10 ` Keir Fraser
2010-05-26 15:02 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100331191019.GA18721@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).