virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Oops
Date: Wed, 10 Jan 2007 11:29:40 +0100	[thread overview]
Message-ID: <45A4C014.9030909@suse.de> (raw)
In-Reply-To: <45A4A0C7.5050405@suse.de>

Gerd Hoffmann wrote:
> 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 ...

Looks like a slot-3 pmd got reused for slot-0, with some stale entries
for the hypervisor hole in there for some reason ...

quick and dirty sledge hammer fix:

--- paravirt-2.6.20-rc4-hg691.orig/arch/i386/paravirt-xen/enlighten.c
+++ paravirt-2.6.20-rc4-hg691/arch/i386/paravirt-xen/enlighten.c
@@ -522,6 +522,7 @@ static fastcall void xen_alloc_pd(u32 pf
 static fastcall void xen_release_pd(u32 pfn)
 {
        make_lowmem_page_readwrite(__va(PFN_PHYS(pfn)));
+       memset(__va(PFN_PHYS(pfn)), 0, PAGE_SIZE);
 }

 static fastcall void xen_release_pt(u32 pfn)

OK, now I'm back to the old buggy state where the ttylinux rootfs fails
to boot up due to init being killed instantly or something like that ...

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>

  reply	other threads:[~2007-01-10 10:29 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   ` Oops Gerd Hoffmann
2007-01-10 10:29     ` Gerd Hoffmann [this message]
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=45A4C014.9030909@suse.de \
    --to=kraxel@suse.de \
    --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).