From: Keir Fraser <keir.xen@gmail.com>
To: sean bruno <seanwbruno@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: Hypervisor Crash, xen4.1
Date: Sun, 22 May 2011 21:05:00 +0100 [thread overview]
Message-ID: <C9FF2AFC.1AC91%keir.xen@gmail.com> (raw)
In-Reply-To: <BANLkTimushzNNYvDaYiMbKOCiMhHhDNUVg@mail.gmail.com>
On 22/05/2011 20:56, "sean bruno" <seanwbruno@gmail.com> wrote:
> Playing around with freebsd non-Xen DomU kernels in hvm mode on the new
> 4.1 hypervisor with a NetBSD -Current Dom0. I keep getting some
> gruesome crashes on it that look like
> this:
Do a debug=y build of Xen so that the backtraces are accurate. Also if you
know how and the crash in notify_via_xen_event_channel comes up often, worth
adding some tracing in there to see which pointer dereference is bad. (Or
you could point me at your xen-syms file associated with your new
backtraces.)
-- Keir
> (XEN) ----[ Xen-4.1.0 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 1
> (XEN) RIP: e008:[<ffff82c4801057a9>] notify_via_xen_event_channel+0x5f/0x91
> (XEN) RFLAGS: 0000000000010246 CONTEXT: hypervisor
> (XEN) rax: 0000000000000000 rbx: 0000000000000001 rcx: 0000010300000000
> (XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: ffff83021f98a188
> (XEN) rbp: ffff83021f98a000 rsp: ffff83021f257be8 r8: 0000000000000004
> (XEN) r9: 000000000000000d r10: 0000000000000001 r11: ffff83021f98a7a8
> (XEN) r12: ffff83021f98a188 r13: 0000000000000001 r14: 0000000000000000
> (XEN) r15: 0000000000000001 cr0: 000000008005003b cr4: 00000000000026f0
> (XEN) cr3: 000000020e945000 cr2: 0000010300000088
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
> (XEN) Xen stack trace from rsp=ffff83021f257be8:
> (XEN) ffff830215f49000 ffff8300d78dc000 ffff8300d78dc000 ffff82c4801997f3
> (XEN) 0000000000000001 0000000000000001 ffff830215f49000 ffff82c4801967ab
> (XEN) ffff83021f257c84 ffff83021f257cf0 0000000000000064 0000000000000000
> (XEN) ffff830215f49000 ffff83021f257cf8 ffff82c4801a5abd ffff8300d78dc000
> (XEN) ffff83021f98a2c0 0000000000000000 ffff8300d78dc000 0000000100000007
> (XEN) ffff8300d78dc000 0000000000000001 ffff83021f257f18 ffff8300d78dc000
> (XEN) ffff83021f257cf8 ffff83021f257f18 000000000000001e ffff82c480196d94
> (XEN) 0000000000000000 ffff83021f257cf8 0000000000000010 ffff82c4801a05b4
> (XEN) ffff83021f257cf8 0000000000000001 0000000012ff8525 0000000000000000
> (XEN) 0000000000000000 ffff8300d78dc000 000000000000001e ffff82c4801b3d75
> (XEN) ffff82c480199daf ffff8300d78dc000 ffff8300d78dc000 ffff82c480291fc0
> (XEN) ffff82c4801b0961 0000000000000001 ffff82c480149817 ffff82c480149817
> (XEN) 0000000000000002 0000000000000000 ffff8302195f5ee0 ffff83021f257db0
> (XEN) ffff82c4802a36c0 ffff82c4802a36c0 ffff82c480115e39 ffff82c4802a44c0
> (XEN) 00000000dfc6c000 0000000000000002 0000000000000000 ffff8300d78dc000
> (XEN) 0000058334f81c83 ffff8300d78dc000 ffff82c4802a36c0 0000058334f820c3
> (XEN) ffff83021f257e70 ffff83021f2e45b0 ffff83021f2cc060 ffff82c48012064b
> (XEN) ffff82c48016bfeb 0000000000000000 0000000000000000 000005832fcc9a59
> (XEN) ffff8300d78dc000 ffff8300dfafc000 0000000000000001 0000000001c9c380
> (XEN) 0000058334f820c3 ffff83021f2cc040 ffff82c48011c908 ffff82c4801a89eb
> (XEN) Xen call trace:
> (XEN) [<ffff82c4801057a9>] notify_via_xen_event_channel+0x5f/0x91
> (XEN) [<ffff82c4801997f3>] hvm_send_assist_req+0x72/0xd1
> (XEN) [<ffff82c4801967ab>] hvmemul_do_io+0x4c1/0x6b7
> (XEN) [<ffff82c4801a5abd>] vlapic_has_pending_irq+0x2c/0x59
> (XEN) [<ffff82c480196d94>] hvmemul_do_pio+0x27/0x2c
> (XEN) [<ffff82c4801a05b4>] handle_pio+0x60/0xce
> (XEN) [<ffff82c4801b3d75>] vmx_vmexit_handler+0x87c/0x1b87
> (XEN) [<ffff82c480199daf>] hvm_do_resume+0x11/0x14b
> (XEN) [<ffff82c4801b0961>] vmx_do_resume+0x12d/0x1fc
> (XEN) [<ffff82c480149817>] context_switch+0x136/0xe8e
> (XEN) [<ffff82c480149817>] context_switch+0x136/0xe8e
> (XEN) [<ffff82c480115e39>] csched_vcpu_wake+0x13f/0x2e1
> (XEN) [<ffff82c48012064b>] add_entry+0x4a/0xa7
> (XEN) [<ffff82c48016bfeb>] __update_vcpu_system_time+0x22e/0x26a
> (XEN) [<ffff82c48011c908>] schedule+0x1ee/0x553
> (XEN) [<ffff82c4801a89eb>] pt_update_irq+0x33/0x1d5
> (XEN) [<ffff82c4801a5abd>] vlapic_has_pending_irq+0x2c/0x59
> (XEN) [<ffff82c4801a132d>] hvm_vcpu_has_pending_irq+0x4d/0xa8
> (XEN) [<ffff82c4801add8c>] vmx_intr_assist+0x49/0x1fd
> (XEN) [<ffff82c4801adb86>] vmx_asm_do_vmentry+0x0/0xda
> (XEN)
> (XEN) Pagetable walk from 0000010300000088:
> (XEN) L4[0x002] = 0000000000000000 ffffffffffffffff
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 1:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: 0000010300000088
> (XEN) ****************************************
> (XEN)
>
>
>
>
> ---------------
>
> (XEN) emulate.c:139:d8 WARNING: io already pending (4)?
> (XEN) Xen BUG at io.c:242
> (XEN) ----[ Xen-4.1.0 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 1
> (XEN) RIP: e008:[<ffff82c4801a05bd>] handle_pio+0x69/0xce
> (XEN) RFLAGS: 0000000000010293 CONTEXT: hypervisor
> (XEN) rax: 0000000000000001 rbx: 0000000000000001 rcx: ffff83021f2cc0d0
> (XEN) rdx: 000000000000000a rsi: 000000000000000a rdi: ffff82c480228244
> (XEN) rbp: ffff83021f257f18 rsp: ffff83021f257ce8 r8: 0000000000000001
> (XEN) r9: 0000000000000000 r10: 00000000fffffffb r11: ffff82c480132706
> (XEN) r12: ffff8300d78d8000 r13: ffff83021f257cf8 r14: ffff83021f257f18
> (XEN) r15: 000000000000001e cr0: 000000008005003b cr4: 00000000000026f0
> (XEN) cr3: 00000002105b4000 cr2: 00000008079c0000
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
> (XEN) Xen stack trace from rsp=ffff83021f257ce8:
> (XEN) ffff83021f257cf8 0000000000000001 0000000000000000 0000000000000000
> (XEN) 0000000000000000 ffff8300d78d8000 000000000000001e ffff82c4801b3d75
> (XEN) ffff82c480199e9b ffff8300d78d8000 ffff8300d78d8000 ffff82c480291fc0
> (XEN) ffff82c4801b0961 0000000000000001 ffff82c480149817 ffff82c480149817
> (XEN) 0000000000000002 0000000000000000 ffff83021549fcb0 ffff83021f257db0
> (XEN) ffff82c4802a36c0 ffff82c4802a36c0 ffff82c480115e39 0000000000000000
> (XEN) 0000000000000000 0000000000000040 ffff82c480145047 ffff83021549fcb0
> (XEN) ffff83021f2d44c0 ffff82c480115902 ffff82c4802a36c0 000097742444678e
> (XEN) ffff83021f257e70 ffff83021f2e45b0 ffff83021f2cc060 ffff82c48012064b
> (XEN) ffff82c48016bfeb 0000000000000002 0000000000000000 000097740e66c72c
> (XEN) ffff8300d78d8000 ffff8300dfafc000 0000000000000001 0000000001c9c380
> (XEN) 000097742444678e ffff82c48014880c ffff8300d78d9790 ffff82c4801a89eb
> (XEN) 000097742445bed9 ffff82c4801a8476 ffff8300d78d8000 ffff8300d78d9868
> (XEN) ffff82c4801a5abd ffff8300d78d8000 ffff83020db3c2c0 ffff82c4801a132d
> (XEN) ffff8300d78d8000 ffff8300d78d8000 fffffe0002a95450 ffff82c4801add8c
> (XEN) ffff82c480280480 ffff82c480284480 0000000000000001 ffff8300d78d8000
> (XEN) ffffff800004faa0 ffffffff80cdacc0 ffffff80f7481cc0 000000000001a3c2
> (XEN) ffffffff80cd8ee0 ffff82c4801adb86 ffffffff80cd8ee0 000000000001a3c2
> (XEN) ffffff80f7481cc0 ffffffff80cdacc0 ffffff800004faa0 ffffffff80ed9480
> (XEN) 0000000000010000 fffffe0002a95450 0000000000000000 fffffe0002b2ec80
> (XEN) Xen call trace:
> (XEN) [<ffff82c4801a05bd>] handle_pio+0x69/0xce
> (XEN) [<ffff82c4801b3d75>] vmx_vmexit_handler+0x87c/0x1b87
> (XEN) [<ffff82c480199e9b>] hvm_do_resume+0xfd/0x14b
> (XEN) [<ffff82c4801b0961>] vmx_do_resume+0x12d/0x1fc
> (XEN) [<ffff82c480149817>] context_switch+0x136/0xe8e
> (XEN) [<ffff82c480149817>] context_switch+0x136/0xe8e
> (XEN) [<ffff82c480115e39>] csched_vcpu_wake+0x13f/0x2e1
> (XEN) [<ffff82c480145047>] __find_next_bit+0x56/0x5f
> (XEN) [<ffff82c480115902>] csched_schedule+0x1b1/0x5a9
> (XEN) [<ffff82c48012064b>] add_entry+0x4a/0xa7
> (XEN) [<ffff82c48016bfeb>] __update_vcpu_system_time+0x22e/0x26a
> (XEN) [<ffff82c48014880c>] vcpu_kick+0x15/0x66
> (XEN) [<ffff82c4801a89eb>] pt_update_irq+0x33/0x1d5
> (XEN) [<ffff82c4801a8476>] pt_timer_fn+0x22/0x2b
> (XEN) [<ffff82c4801a5abd>] vlapic_has_pending_irq+0x2c/0x59
> (XEN) [<ffff82c4801a132d>] hvm_vcpu_has_pending_irq+0x4d/0xa8
> (XEN) [<ffff82c4801add8c>] vmx_intr_assist+0x49/0x1fd
> (XEN) [<ffff82c4801adb86>] vmx_asm_do_vmentry+0x0/0xda
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 1:
> (XEN) Xen BUG at io.c:242
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-05-22 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 19:56 Hypervisor Crash, xen4.1 sean bruno
2011-05-22 20:05 ` Keir Fraser [this message]
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=C9FF2AFC.1AC91%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=seanwbruno@gmail.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).