From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.33-rc2: Xen/Guest switching to user mode with no user page tables
Date: Wed, 06 Jan 2010 14:38:29 +1100 [thread overview]
Message-ID: <4B4405B5.9040205@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.01.1001051649100.3483@bogon.housecafe.de>
On 01/06/2010 12:03 PM, Christian Kujau wrote:
> Hi there,
>
> a bit late with the testing again, I just found out that my Xen
> DomU won't boot with 2.6.33-rc2. The last working one is 2.6.32, I'll try
> to bisect if needed.
>
> The booting stops at:
>
> [ 0.010000] no hardware sampling interrupt available.
> [ 0.010000] Intel PMU driver.
> [ 0.010000] ... version: 2
> [ 0.010000] ... bit width: 40
> [ 0.010000] ... generic registers: 2
> [ 0.010000] ... value mask: 000000ffffffffff
> [ 0.010000] ... max period: 000000007fffffff
> [ 0.010000] ... fixed-purpose events: 3
> [ 0.010000] ... event mask: 0000000700000003
> [ 0.011314] Freeing SMP alternatives: 24k freed
>
>
> And "xm dmesg" says:
>
> xen# xm dmesg
> (XEN) traps.c:244:d88 Guest switching to user mode with no user page tables
> (XEN) traps.c:273:d88 Fatal error
>
*Really* weird. No idea how it could get into that state... I've never
seen this message before, even during development. I'd suspect either a
compiler bug, a miscompile, or some bad interaction with another patch.
A bisection would be useful.
> (XEN) domain_crash called from traps.c:274
> (XEN) Domain 88 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.2.1-rc1-pre x86_64 debug=n Not tainted ]----
> (XEN) CPU: 0
> (XEN) RIP: e033:[<ffffffff810012eb>]
> (XEN) RFLAGS: 0000000000240246 CONTEXT: guest
> (XEN) rax: 0000000000000017 rbx: 0000000000000000 rcx: ffffffff810012eb
> (XEN) rdx: 0000000000000000 rsi: ffffffff810488a0 rdi: 0000000000000000
> (XEN) rbp: 0000000000000000 rsp: ffff88000f83df90 r8: 0000000000000000
> (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000240246
> (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
> (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026b0
> (XEN) cr3: 0000000096ba9000 cr2: 0000000000000000
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=ffff88000f83df90:
> (XEN) 0000000000000000 0000000000000202 ffffffff81009880 0000000000000100
> (XEN) ffffffff81009880 0000000000000033 0000000000000202 0000000000000000
> (XEN) 000000000000002b ffffffff81009880 0000000000000011 0000000000000202
> (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 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 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# gdb vmlinux.2010-01-05.6451
> (no debugging symbols found)
> (gdb) x/i 0xffffffff810012eb
> 0xffffffff810012eb<hypercall_page+747>: add %al,(%rax)
>
>
> The Dom0 is running a 2.6.24-24-xen Ubuntu kernel amd I'm kinda reluctant
> to upgrade, as I don't have a serial console to this MacMini, if things go
> wrong :-\
>
> I've put the .config (make oldconfig from 2.6.32) and dmesg on:
>
> http://nerdbynature.de/bits/2.6.33-rc2/xen/
>
J
next prev parent reply other threads:[~2010-01-06 3:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 1:03 2.6.33-rc2: Xen/Guest switching to user mode with no user page tables Christian Kujau
2010-01-06 3:38 ` Jeremy Fitzhardinge [this message]
2010-01-06 3:48 ` Christian Kujau
2010-01-06 5:14 ` Jeremy Fitzhardinge
2010-01-06 11:06 ` Christian Kujau
2010-01-06 11:21 ` Cyrill Gorcunov
2010-01-06 12:43 ` Christian Kujau
2010-01-07 19:06 ` Christian Kujau
2010-01-07 19:20 ` Cyrill Gorcunov
2010-01-07 19:31 ` Christian Kujau
2010-01-07 19:34 ` Cyrill Gorcunov
2010-01-07 19:19 ` H. Peter Anvin
2010-01-07 19:30 ` Christian Kujau
2010-01-08 21:50 ` Cyrill Gorcunov
2010-01-09 23:55 ` Christian Kujau
2010-01-10 1:50 ` Brian Gerst
2010-01-10 8:09 ` Cyrill Gorcunov
2010-01-10 12:59 ` Ian Campbell
2010-01-10 13:36 ` Cyrill Gorcunov
2010-01-10 13:49 ` Cyrill Gorcunov
2010-01-10 14:05 ` Ian Campbell
2010-01-15 8:36 ` Christian Kujau
2010-01-15 11:29 ` Ian Campbell
2010-01-15 12:03 ` Cyrill Gorcunov
2010-01-15 12:00 ` Cyrill Gorcunov
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=4B4405B5.9040205@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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