virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Oops
Date: Wed, 10 Jan 2007 09:16:07 +0100	[thread overview]
Message-ID: <45A4A0C7.5050405@suse.de> (raw)
In-Reply-To: <45A41B60.3070500@goop.org>

[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]

Jeremy Fitzhardinge wrote:
> Gerd Hoffmann wrote:
>>   Hi,
>>
>> paravirt kernel doesn't boot as xen guest for me, see attachment.
>>   
> 
> Hm, I just booted a pae kernel from the current paravirt repo and got it
> to usermode.  What's your .config?  Also, what line is getting the fault?

config is attached.

It faults in fork syscall, down in pgd_walk().  It finds a pmd entry
pointing to a machine page where the mfn_to_pfn translation returns -1
aka 0xffffffff.  Trying to find a struct page for that one doesn't work ...

kernel with debug printk's:

xen_pgd_pin c1abb000
   g     0:  1abe001 1ae61001                <- pgd (index, val, val_ma)
     m   0:   80b067 1a394067                <- pmd (same)
     m   1:   80c067 1a393067
     m   2:   80d067 1a392067
     m   3:   80e067 1a391067
     m   4:   80f067 1a390067
     m   5:     2067 1b621067
     m   6:     3067 1b620067
     m   7:     4067  dbf7067
     m   8:     5067  dbf6067
     m   9:     6067  dbf5067
     m  10:     7067  dbf4067
     m  11:     8067 19c57067
     m  12:     9067 19c56067
     m  13:     a067 19c55067
     m  14:     b067 19c54067
     m  15:     c067 1a57f067
     m  20:  107e067 19d21067
     m  64:  1808067 1d297067
     m 426:     e067 1a57d067
     m 427:     d067 1a57e067
mfn_to_pfn: mfn 3f400 pfn ffffffff
mfn_to_pfn: mfn 3f400 pfn ffffffff
     m 428: fffff0a1 3f4000a1                <- here is the broken one

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>

[-- Attachment #2: pae.config --]
[-- Type: application/x-config, Size: 20112 bytes --]

[-- Attachment #3: Type: text/plain, Size: 165 bytes --]

_______________________________________________
Virtualization mailing list
Virtualization@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/virtualization

  reply	other threads:[~2007-01-10  8:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 13:34 Oops Gerd Hoffmann
2007-01-09 22:46 ` Oops Jeremy Fitzhardinge
2007-01-10  8:16   ` Gerd Hoffmann [this message]
2007-01-10 10:29     ` Oops Gerd Hoffmann
2007-01-10 13:05       ` Oops Gerd Hoffmann
2007-01-10 20:07         ` Oops Jeremy Fitzhardinge
2007-01-10 23:52         ` Oops Chris Wright
2007-01-10 23:53           ` Oops Jeremy Fitzhardinge
2007-01-11  8:13             ` Oops Gerd Hoffmann
2007-01-11  8:11           ` Oops Gerd Hoffmann
2007-01-11 15:45           ` Oops Gerd Hoffmann
2007-01-11 17:41             ` Oops Chris Wright
2007-01-12  8:24               ` Oops Gerd Hoffmann
2007-01-12  2:53             ` Oops Rusty Russell
2007-01-12  4:23               ` Oops Chris Wright
2007-01-12  8:31                 ` Oops Gerd Hoffmann
2007-01-10 20:06       ` Oops Jeremy Fitzhardinge
2007-01-10 21:44       ` Oops Jeremy Fitzhardinge
2007-01-11 14:12         ` Oops Gerd Hoffmann
2007-01-11 19:56           ` Oops Jeremy Fitzhardinge
2007-01-10 19:38     ` Oops 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=45A4A0C7.5050405@suse.de \
    --to=kraxel@suse.de \
    --cc=jeremy@goop.org \
    --cc=virtualization@lists.osdl.org \
    /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;
as well as URLs for NNTP newsgroup(s).