From: Andrew Theurer <habanero@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: David F Barrera <dfbp@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: domU can't start, Non-priv warnings
Date: Wed, 17 Aug 2005 14:53:04 -0500 [thread overview]
Message-ID: <430395A0.2030806@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282BB7@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>
>
> Do you not get a couple of lines from Xen imediately preceeding the
> crash? Might be worth a debug=y build.
I'll make sure debug=y is on. I also noticed I did not limit this
system to 3g (it has 4g). I recall this being a problem recently. I'll
limit my memory and try again.
the xen output:
(XEN) (file=traps.c, line=880) Non-priv domain attempted
RDMSR(00000000c0000080.
(XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000
(XEN) Domain 2 (vcpu#0) crashed on cpu#3:
(XEN) CPU: 3
BTW, has anyone tried compiling xenU x86_64 kernels with debug on? I
error out on, hmm, can't recall the file right now, maybe entry.S. More
info on that shortly.
-Andrew
>
> Ian
>
>>> Please could you lookup the symbols for the eip and maybe the first
>>> couple of text addresses on the stack.
>>>
>> I reproduced with a recent pull:
>>
>> Latest ChangeSet: Wed Aug 17 13:22:18 2005
>> fbdbe4fc218de40d5176e0104908e05fb6e2c6ce
>>
>> Looks like we are stuck in xen_l1_entry_update():
>>
>> void xen_l1_entry_update(pte_t *ptr, pte_t val) {
>> mmu_update_t u;
>> u.ptr = virt_to_machine(ptr);
>> u.val = pte_val_ma(val);
>> BUG_ON(HYPERVISOR_mmu_update(&u, 1, NULL, DOMID_SELF) < 0); }
>>
>> ...assuming we are hitting the BUG
>>
>> stack trace:
>>
>> xen_l1_entry_update
>> __set_fixmap
>> acpi_find_rsdp
>> acpi_table_init
>> acpi_boot_table_init
>> setup_arch
>> level3_kernel_pgt
>> init_task
>> start_kernel
>>
>> (XEN) Domain 3 (vcpu#0) crashed on cpu#3:
>> (XEN) CPU: 3
>> (XEN) EIP: e033:[<ffffffff8011ee91>] ???
>> (XEN) EFLAGS: 0000000000000282
>> (XEN) rax: 00000000ffffffea rbx: ffffffffff578000 rcx:
>> ffffffff8011ee8d r0
>> (XEN) rsi: 0000000000000001 rdi: ffffffff80599e90 rbp:
>> 8000000000000067 r8
>> (XEN) r8: 0000000000000100 r9: 0000000000020000 r10:
>> 0000000000007ff0 r6
>> (XEN) r12: ffff880001703fd0 r13: ffff880001704bc0 r14:
>> 8000000000000067 r0
>> (XEN) Guest stack trace from rsp=ffffffff80599e58:
>> (XEN) ffffffff8011ee8d 0000000000000206 ffffffff8011ee91
>> 000000010000e030 00
>> (XEN) 8000000000000067 00000000001eb000 ffffffff8011c9aa
>> 0000000000000000 00
>> (XEN) ffffffff805c226e 0000000000000e00 ffffffff805cab75
>> 0000000000001000 00
>> (XEN) ffffffff805c22a3 0000000000000e00 ffffffff805c1115
>> 00000000d7c93830 ff
>> (XEN) ffffffff80103000 ffffffff0000000f 0000000007020800
>> ffffffff8047cc00 ff
>> (XEN) ffffffff805ba558 ffffffff80537740 ffffffff805ba193
>> 80108e0000100038 00
>> (XEN) 0000000000000000 0000000000000000 0000000000000000
>> 0000000000000000 00
>>
>>
>
next prev parent reply other threads:[~2005-08-17 19:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 19:39 domU can't start, Non-priv warnings Ian Pratt
2005-08-17 19:53 ` Andrew Theurer [this message]
2005-08-17 19:58 ` Chris Wright
-- strict thread matches above, loose matches on Subject: below --
2005-08-17 7:41 Petersson, Mats
2005-08-17 11:59 ` Jerone Young
2005-08-17 17:13 ` Jerone Young
2005-08-16 21:32 Ian Pratt
2005-08-17 19:35 ` Andrew Theurer
2005-08-16 20:23 Nakajima, Jun
2005-08-16 19:19 Andrew Theurer
2005-08-16 19:32 ` Jerone Young
2005-08-16 19:45 ` Keir Fraser
2005-08-16 19:56 ` Andrew Theurer
2005-08-16 20:02 ` Jerone Young
2005-08-16 20:01 ` David F Barrera
2005-08-16 21:24 ` Andrew Theurer
2005-08-16 21:53 ` David F Barrera
2005-08-16 21:52 ` Keir Fraser
2005-08-16 21:59 ` David F Barrera
2005-08-16 22:14 ` Keir Fraser
2005-08-17 16:54 ` David F Barrera
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=430395A0.2030806@us.ibm.com \
--to=habanero@us.ibm.com \
--cc=dfbp@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.