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


[Xen-bugs] [Bug 366] kernel BUG at arch/xen/kernel/smpboot.c:186 (vcpu_p

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 366] kernel BUG at arch/xen/kernel/smpboot.c:186 (vcpu_prepare)!
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 15 Nov 2005 21:10:35 +0000
Delivery-date: Tue, 15 Nov 2005 21:10:39 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From grimm@xxxxxxxxxx  2005-11-15 21:10 -------
Created an attachment (id=107)
 --> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=107&action=view)
flush writeable pagetables state patch 

I applied the attached patch to changeset 7701 to see if it solved this bug.  

Instead of the vcpu_prepare issue, now dom0 crashes with the following output:

Checking 'hlt' instruction... disabled
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff125705>] set_gdt+0x225/0x4c0
(XEN) EFLAGS: 00010286   CONTEXT: hypervisor
(XEN) eax: f6800000   ebx: 80000002   ecx: ffba3500   edx: fffffffd
(XEN) esi: f67fffe8   edi: ffb8b080   ebp: 00000000   esp: ff103f24
(XEN) cr0: 8005003b   cr3: 03f22000
(XEN) ds: e010   es: e010   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff103f24:
(XEN)    f682b1b8 a0000000 80000002 ffbb2080 00000001 00000297 00000015 8000001

(XEN)    00003f22 f685eb30 ffb8b080 ff11ec81 ffb8b080 ffb80ad0 00000020 8000001

(XEN)    ffbb2080 ffb80080 ffbb2080 ffb8b080 ffffffef ffbb2080 00000015 ff10beb

(XEN)    ffb8b080 ffb80080 00000af0 c079d000 00000012 ffb8b080 ffb80080 ffbb008

(XEN)    00000015 c010a1ac 00000061 ff13f133 00000000 00000015 c071f49c 0000001

(XEN)    c010a1ac 00000061 00000018 000e0000 c01076e6 00000061 00000206 c071f48

(XEN)    00000069 0000007b 0000007b 00000000 00000000 00000000 ffbb0080
(XEN) Xen call trace:
(XEN)    [<ff125705>] set_gdt+0x225/0x4c0
(XEN)    [<ff11ec81>] arch_set_info_guest+0x1c1/0x530
(XEN)    [<ff10beb4>] do_vcpu_op+0x164/0x1d0
(XEN)    [<ff13f133>] hypercall+0x53/0x57
(XEN) Pagetable walk from f67ffff8:
(XEN)  L3 = 0000000003f26001
(XEN)   L2 = 0000000000000000
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) [error_code=0000]
(XEN) Faulting linear address: f67ffff8
(XEN) ****************************************
(XEN) Reboot in five seconds...

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>