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] Crash in modified Xen

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Crash in modified Xen
From: Cutter 409 <cutter409@xxxxxxxxx>
Date: Fri, 28 Jan 2011 19:11:41 -0500
Delivery-date: Fri, 28 Jan 2011 16:12:38 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=1bRwplZvBnUsveZzkgt1mHRcbCWDFI1xZedu6KnBUeU=; b=sjWKXpuyTVqGMHlJULWo2diHAhJBnnCx1xfWOW0VlBOmAQXek19FNL2IFeWQGUC5Jh prC81mcOYVjd0zep6vieKm04qCKPaBZBOco8MCUx2BdEiAfubkBnm1Jg7NQeIVagztFQ /QoibEDR5cVns0qMLY+zELMxTRhcBqmNVbUXw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=AyMH9jEoST5fCma9mq4NEelFk3cmY8+mGsQvOnSFhesfp1Ji51lk8AlbGfUbaWXs8u z5lBviYu72k8s8e/pPnvTg4t9OSuw/mRBiFbrhAe36gUo6PLxtseoe1g/J56BtY7U78U i4//vjOgElx1Lo5w6onrIZqY2YTphQB5Bvfp8=
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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I'm getting a crash with a version of Xen that I've been playing around with, which happens intermittently when a domain is being destroyed.
It has happened both while shutting down the guest properly and while forcing a domain to shutdown/reboot.

I'm not touching allocating domheap pages at all, however I do allocate xenheap pages and share them with dom0.

Does anyone know if there's some pitfall that could be causing a crash like this?

Thanks!

(XEN) ----[ Xen-3.4.2  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff828c80141819>] relinquish_memory+0x69/0x460
(XEN) RFLAGS: 0000000000010202   CONTEXT: hypervisor
(XEN) rax: ffff828400000000   rbx: ffff8284006e11e0   rcx: c000000000000002
(XEN) rdx: ffff82a3ffffffe0   rsi: ffff8284006e11c8   rdi: ffff830051272000
(XEN) rbp: ffff830051272000   rsp: ffff828c80277d48   r8:  ffff8284006e11c8
(XEN) r9:  00ffffffffffffff   r10: ffff828c801f33b0   r11: 0000000000000000
(XEN) r12: ffff830051272018   r13: ffff828c80277f28   r14: ffff830051272014
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000026f0
(XEN) cr3: 000000007b458000   cr2: ffff82a3ffffffe4
(XEN) ds: 007b   es: 007b   fs: 00d8   gs: 0033   ss: 0000   cs: e008
(XEN) Xen stack trace from rsp=ffff828c80277d48:
(XEN)    ffff830051273208 000000008014f492 ffff8284004e3df0 8000000000000000
(XEN)    000000000004c2de ffff830051272000 ffff830051272018 ffff828c80277e28
(XEN)    0000000000000000 0000000000000000 0000000000000000 ffff828c80141efc
(XEN)    ffff830051272000 0000000000000000 ffff828c80277e28 ffff828c8010619d
(XEN)    0000000000000005 ffff828c00000000 0000000000000001 fffffffffffffff3
(XEN)    00000000aab44fac ffff828c80104922 ffff83007b456000 0000000000000000
(XEN)    00007ff07b2fc660 ffff828c8014da68 ffff828c802495a8 ffff83007a7a0000
(XEN)    0000000500000002 0000000000000002 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 ffff828c80277f28 ffff828c80124c43
(XEN)    0000000200000000 ffff828c80277f28 ffff828c80277f28 ffff828c8024902c
(XEN)    0000000000000000 ffff83007b456000 00000000c607df20 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 ffff828c801eb5f3
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    00000000c607df20 00000000aab44fac 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000024 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000010000000000
(XEN)    00000000c0101487 0000000000000061 0000000000000282 00000000c607dd6c
(XEN) Xen call trace:
(XEN)    [<ffff828c80141819>] relinquish_memory+0x69/0x460
(XEN)    [<ffff828c80141efc>] domain_relinquish_resources+0x14c/0x1e0
(XEN)    [<ffff828c8010619d>] domain_kill+0x6d/0x180
(XEN)    [<ffff828c80104922>] do_domctl+0x812/0x10e0
(XEN)    [<ffff828c8014da68>] get_page+0x28/0xd0
(XEN)    [<ffff828c80124c43>] compat_multicall+0x183/0x350
(XEN)    [<ffff828c801eb5f3>] compat_hypercall+0x83/0x90
(XEN)
(XEN) Pagetable walk from ffff82a3ffffffe4:
(XEN)  L4[0x105] = 000000007b482027 5555555555555555
(XEN)  L3[0x08f] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0002]
(XEN) Faulting linear address: ffff82a3ffffffe4
(XEN) ****************************************

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Crash in modified Xen, Cutter 409 <=