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

[Xen-devel] [PATCH] Xen on a 32-way and bitops

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] Xen on a 32-way and bitops
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Fri, 21 Oct 2005 17:06:49 -0400
Delivery-date: Fri, 21 Oct 2005 21:04:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: AcXWg1nj3+xBXWapSk2CBTAjlTQEDg==
Thread-topic: [PATCH] Xen on a 32-way and bitops
I was trying to bring Xen up on an ES7000 with 32 logical processors and
16GB of RAM. Xen dies on "Assertion 'offset < size' failed, line 32,
file bitops.c" (see below). I think the assertion should be "offset <=
size". I have attached a patch that does this.

Signed off by: Aravindh Puthiyaparambil
<aravindh.puthiyaparambil@xxxxxxxxxx>



(XEN) Assertion 'offset < size' failed, line 32, file bitops.c
(XEN) BUG at bitops.c:32
(XEN) CPU:    0
(XEN) RIP:    e010:[<ffff83000012cc95>] __find_next_bit+0x7d/0x104
(XEN) RFLAGS: 0000000000010282   CONTEXT: hypervisor
(XEN) rax: ffff8300001ac564   rbx: 0000000000000101   rcx:
0000000000003267
(XEN) rdx: 0000000000000000   rsi: 0000000000000001   rdi:
ffff8300001ac564
(XEN) rbp: ffff830000107df8   rsp: ffff830000107dc8   r8:
00000000ffffffff
(XEN) r9:  00000000ffffffff   r10: ffff8300001ccc9f   r11:
ffff8300001cc8b0
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14:
0000000000000000
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr3:
0000000000102000
(XEN) Xen stack trace from rsp=ffff830000107dc8:
(XEN)    ffff830000107e28 0000001f0019999a 0000000000000020
ffff8300001e9f80
(XEN)    0000002000000020 ffff8300001e9f80 ffff830000107e28
ffff83000014d0b4
(XEN)    ffff830000107e28 000000200014d038 ffff8300001e9f80
0000001f001e9f80
(XEN)    ffff830000107e48 ffff83000019324e 0000001f00fff000
0000000000000000
(XEN)    ffff830000107f28 ffff830000193c17 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000100000000 ffff8300001e71f0
00000000000000b4
(XEN)    0000000000408000 0000000000100000 0000000800000000
000000010000006e
(XEN)    0000000000000003 00000000000002f8 000000f000000000
0000000900000009
(XEN)    0000000001000000 0000000100000000 0000000100000000
0000000000000000
(XEN)    0000000000000000 00000000017444a0 0000000001000000
00000000007444a0
(XEN)    0000000000000d91 ffff830000020e40 0000000000000000
ffff83000002bfe0
(XEN)    0000000000067ec8 ffff8300001002b8 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 ffff8300001be700
(XEN) Xen call trace:
(XEN)    [<ffff83000012cc95>] __find_next_bit+0x7d/0x104
(XEN)    [<ffff83000014d0b4>] __next_cpu+0x23/0x25
(XEN)    [<ffff83000019324e>] start_of_day+0x1f8/0x2ea
(XEN)    [<ffff830000193c17>] __start_xen+0x8d7/0xbaf
(XEN)    [<ffff8300001002b8>] __high_start+0x94/0x96
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) CPU0 FATAL TRAP: vector = 6 (invalid operand)
(XEN) [error_code=0000]
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

Attachment: bitops.c.diff
Description: bitops.c.diff

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] Xen on a 32-way and bitops, Puthiyaparambil, Aravindh <=