From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xen-devel@lists.xensource.com, Chris Wright <chrisw@sous-sol.org>
Subject: Re: [Xen-devel] [PATCH] let XEN depend on PAE
Date: Fri, 22 Feb 2008 13:13:52 -0800 [thread overview]
Message-ID: <47BF3B10.7070402@goop.org> (raw)
In-Reply-To: <47BF266F.5020806@nets.rwth-aachen.de>
Arnd Hannemann wrote:
> Jeremy Fitzhardinge wrote:
>
>> Arnd Hannemann wrote:
>>
>>> This is with 2.6.24.2, but latest-git looks the same:
>>> I also tried with 2.6.23 which crashes instantly, without any output
>>> of the guest.
>>>
>>>
>> I'm not too surprised. Non-PAE Xen is a bit of a rarity, and it only
>> gets tested rarely. Chris Wright did spend some time on it a while ago,
>> but I don't know that its had any real attention since. I've been
>> making sure non-PAE compiles, but I've been lax about testing it.
>> This is the first usermode exec, I guess? The backtrace is a bit odd;
>> I've never seen a problem in move_page_tables before.
>>
>
> Yes its trying to execute the first script in initramfs, I also tried with initramdisk
> and got a similar error. (move_page_tables also involved)
>
>
>> Does "xm dmesg" tell you what Xen is complaining about? You may need to
>> compile with debug=y in Config.mk.
>>
>
> (XEN) mm.c:645:d44 Non-privileged (44) attempt to map I/O space 00000000
>
> I will recompile with debug=y and post the output.
> If I reduce the dom0 memory with dom0_mem=200000 I see something like
> 00000080 with dom0_mem=800000 I always see 00000000.
>
That's helpful. Looks like the mfn is getting mushed to 0.
J
next prev parent reply other threads:[~2008-02-22 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 11:00 [PATCH] let XEN depend on PAE Arnd Hannemann
2008-02-22 13:37 ` Ian Campbell
2008-02-22 15:00 ` Arnd Hannemann
2008-02-22 16:37 ` [Xen-devel] " Jeremy Fitzhardinge
2008-02-22 16:54 ` Arnd Hannemann
2008-02-22 18:59 ` Jeremy Fitzhardinge
2008-02-22 19:45 ` Arnd Hannemann
2008-02-22 21:13 ` Jeremy Fitzhardinge [this message]
2008-02-23 12:37 ` Arnd Hannemann
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=47BF3B10.7070402@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=hannemann@nets.rwth-aachen.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox