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 14:24:58 -0400	[thread overview]
Message-ID: <486D197A.7040808@theshore.net> (raw)
In-Reply-To: <486D0DA6.7010901@goop.org>

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

> For reference:
> 
> $ gdb 2.6.26-rc8-linode11 GNU gdb Fedora (6.8-10.fc9)
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i386-redhat-linux-gnu"...
> (no debugging symbols found)
> (gdb) x/i 0x00000000c0103b55                        <- note: need to add 
> 0x to start
> 0xc0103b55 <make_lowmem_page_readonly+85>:    ud2a   (gdb) disassemble 
> make_lowmem_page_readonly
> Dump of assembler code for function make_lowmem_page_readonly:
> 0xc0103b00 <make_lowmem_page_readonly+0>:    push   %ebp
> 0xc0103b01 <make_lowmem_page_readonly+1>:    mov    %eax,%ebp
> 0xc0103b03 <make_lowmem_page_readonly+3>:    push   %edi

Cool, thanks :)

-Chris

  parent reply	other threads:[~2008-07-03 18:24 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 18:24       ` Christopher S. Aker
2008-07-03 18:24       ` Christopher S. Aker [this message]
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 17:34     ` Jeremy Fitzhardinge
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=486D197A.7040808@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.