All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
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:39:25 -0700	[thread overview]
Message-ID: <486D2AED.4020407@goop.org> (raw)
In-Reply-To: <486D197A.7040808@theshore.net>

Christopher S. Aker wrote:
> Jeremy Fitzhardinge wrote:
>>>> Were there any other errors/warnings printed here?
>>>
>>> Nope.  Just some whitespace.
>>
>> Are you sure?  Could you send a full xm dmesg log output?  The crash 
>> is from a BUG() caused by a failing hypercall.  Since you have 
>> compiled Xen with debug enabled, it should have printed something 
>> about why it was failing the hypercall.
>
> Unfortunately, I included the entire dmesg output from that xm create 
> run.  Here's more of the transcript in case it's useful:
>
> http://www.theshore.net/~caker/xen/pvops-bug1/log.txt
>
> Although, looking at it again, I did miss this line:
>
> (XEN) mm.c:645:d341 Non-privileged (341) attempt to map I/O space 
> 000d2e50

Good, that's what I was hoping to see.  (Well, actually not that 
*particular* message, which is strange, but some explanatory message at 
least.)

    J

  parent reply	other threads:[~2008-07-03 19:39 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 15:44 ` Jeremy Fitzhardinge
2008-07-03 16:00   ` Christopher S. Aker
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 19:39         ` Jeremy Fitzhardinge
2008-07-03 19:39         ` Jeremy Fitzhardinge [this message]
2008-07-03 20:38           ` Christopher S. Aker
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 18:24       ` Christopher S. Aker
2008-07-03 16:00   ` Christopher S. Aker

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=486D2AED.4020407@goop.org \
    --to=jeremy@goop.org \
    --cc=caker@theshore.net \
    --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.