All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher S. Aker" <caker@theshore.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: 2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap
Date: Thu, 03 Jul 2008 12:00:09 -0400	[thread overview]
Message-ID: <486CF789.7030700@theshore.net> (raw)
In-Reply-To: <486CF3F7.3030309@goop.org>

Jeremy Fitzhardinge wrote:
> Is this consistent or sporadic?  

Consistently fails to boot, across a few test boxes, slightly different 
Xen versions -- all around Xen 3.2.1, same config.

> Does it depend on how much guest memory you give it?

No.  Tried with 128, 360, 5000.  They all fail in the same way.

> What was the last kernel version which worked?

I built a 2.6.25.10 pv_ops this morning and it boots fine.

> Were there any other errors/warnings printed here?

Nope.  Just some whitespace.

>> (XEN) traps.c:413:d332 Unhandled invalid opcode fault/trap [#6] on 
>> VCPU 0 [ec=0000]
>> (XEN) domain_crash_sync called from entry.S
>> (XEN) Domain 332 (vcpu#0) crashed on cpu#0:
>> (XEN) ----[ Xen-3.2.1-rc5  x86_64  debug=y  Not tainted ]----
>> (XEN) CPU:    0
>> (XEN) RIP:    e019:[<00000000c0103b55>]
> 
> Could you decode this to see which function this corresponds to?

I'd love to know how for future reference, but for now I've placed the 
files here:

http://www.theshore.net/~caker/xen/pvops-bug1/

Thanks,
-Chris

  parent reply	other threads:[~2008-07-03 16:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 14:38 2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap Christopher S. Aker
2008-07-03 15:44 ` Jeremy Fitzhardinge
2008-07-03 16:00   ` Christopher S. Aker
2008-07-03 16:00   ` Christopher S. Aker [this message]
2008-07-03 17:34     ` Jeremy Fitzhardinge
2008-07-03 17:34     ` Jeremy Fitzhardinge
2008-07-03 18:24       ` Christopher S. Aker
2008-07-03 18:24       ` Christopher S. Aker
2008-07-03 19:39         ` Jeremy Fitzhardinge
2008-07-03 20:38           ` Christopher S. Aker
2008-07-03 21:04             ` Jeremy Fitzhardinge
2008-12-18 15:31               ` Guillaume Rousse
2008-12-19 21:26                 ` Jeremy Fitzhardinge
2008-12-20 13:37                   ` Guillaume Rousse
2008-12-20 19:43                     ` Jeremy Fitzhardinge
2008-12-23 14:17                       ` Guillaume Rousse
2008-12-31 21:45                         ` Jeremy Fitzhardinge
2008-07-03 21:04             ` Jeremy Fitzhardinge
2008-07-03 20:38           ` Christopher S. Aker
2008-07-03 19:39         ` Jeremy Fitzhardinge
2008-07-03 15:44 ` Jeremy Fitzhardinge

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=486CF789.7030700@theshore.net \
    --to=caker@theshore.net \
    --cc=jeremy@goop.org \
    --cc=virtualization@lists.linux-foundation.org \
    --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.