From: Jeremy Fitzhardinge <jeremy@goop.org>
To: John Morrison <john@clustered.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: Unhandled invalid opcode fault/trap
Date: Sun, 08 Feb 2009 10:03:10 -0800 [thread overview]
Message-ID: <498F1E5E.1040902@goop.org> (raw)
In-Reply-To: <87812E6B-4A96-4733-B2DD-0447CCC1AD1F@clustered.net>
John Morrison wrote:
>
> Hi,
>
> Trying to get pv_ops working with 2.6.28.4, this is what I get on an
> Intel Xeon CPU.
>
> Works fine on AMD Opteron...
>
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen)
> (XEN) Freed 104kB init memory.
> (XEN) mm.c:1482:d1 Bad L1 flags 800000
> (XEN) traps.c:437:d1 Unhandled invalid opcode fault/trap [#6] on VCPU
> 0 [ec=0000]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 1 (vcpu#0) crashed on cpu#7:
> (XEN) ----[ Xen-3.3.1 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 7
> (XEN) RIP: e033:[<ffffffff8020aa1a>]
> (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest
> (XEN) rax: 00000000ffffffea rbx: 8000000000000161 rcx:
> 00000000007ff000
> (XEN) rdx: 0000000000000000 rsi: 80000008053e2061 rdi:
> ffffffff804f0000
> (XEN) rbp: ffffffff8048ffa8 rsp: ffffffff8048ff58 r8:
> 0000000000000000
> (XEN) r9: 0000000000000000 r10: 0000000000000000 r11:
> 0000000000000000
> (XEN) r12: ffffffff804f0000 r13: 0000000000001000 r14:
> 0000000000000008
> (XEN) r15: 0000000000000008 cr0: 000000008005003b cr4:
> 00000000000026b0
> (XEN) cr3: 000000080517e000 cr2: 0000000000000000
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=ffffffff8048ff58:
> (XEN) 00000000007ff000 0000000000000000 ffffffff8020aa1a
> 000000010000e030
> (XEN) 0000000000010082 ffffffff8048ff98 000000000000e02b
> ffffffff8020aa16
> (XEN) 0000000000000200 0000000000000040 ffffffff8048fff8
> ffffffff804b51c5
> (XEN) ffffffff80754000 0000080000000000 0000000000040000
> 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN) 0000000000000000
>
> Any ideas ?
Do you have NX disabled in your BIOS (or is it a very early x86-64 intel
chip)?
What does:
$ gdb vmlinux
(gdb) x/i 0xffffffff8020aa1a
say?
J
prev parent reply other threads:[~2009-02-08 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 4:02 Unhandled invalid opcode fault/trap John Morrison
2009-02-08 18:03 ` Jeremy Fitzhardinge [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=498F1E5E.1040902@goop.org \
--to=jeremy@goop.org \
--cc=john@clustered.net \
--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.