From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Error getting mfn
Date: Tue, 18 Sep 2012 09:36:50 -0400 [thread overview]
Message-ID: <20120918133650.GC12053@phenom.dumpdata.com> (raw)
In-Reply-To: <CAJ75kXZm-BqWdL2O41XkSE1VCdd4ruW=+CqDmR1b3=701RnXmw@mail.gmail.com>
On Tue, Sep 18, 2012 at 10:24:42AM +0200, William Dauchy wrote:
> Hello,
>
> I'm getting many "Error getting mfn" on a xen4.1.3 with dom0 3.4.11 x86_32.
You need to provide more. The full serial log please, and also the
.config.
Since this is 32-bit, I wonder if you are hitting the CONFIG_NUMA issue...
but I think you reported it some time ago and did you try the fix?
> I thought it could be related to
> xen/mmu: Release just the MFN list, not MFN list and part of pagetables.
> http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=785f62314984ea3af9dd830b020289ba2509ae69
That shouldn't be it - b/c the URL you mentioned is for the set of patches
that are destined for v3.7.
>
> (XEN) Freed 212kB init memory.
> (XEN) mm.c:908:d0 Error getting mfn 2009b (pfn 5555555555555555) from
> L1 entry 000000002009b023 for l1e_owner=0, pg_owner=0
> (XEN) mm.c:908:d0 Error getting mfn 2009c (pfn 5555555555555555) from
> L1 entry 000000002009c023 for l1e_owner=0, pg_owner=0
> [...]
> (XEN) mm.c:908:d0 Error getting mfn c32116 (pfn 5555555555555555) from
> L1 entry 8000000c32116063 for l1e_owner=0, pg_owner=0
> (XEN) mm.c:908:d0 Error getting mfn c32117 (pfn 5555555555555555) from
> L1 entry 8000000c32117063 for l1e_owner=0, pg_owner=0
Please use 'sync_console loglvl=all dom0_max_vcpus=1 console=com1 com1=xxxxx' and on the Linux command line:
'console=hvc0 debug loglevel=8"
> (XEN) ../physdev.c:171: dom0: wrong map_pirq type 3
>
> Any hint?
>
> Regards,
> --
> William
next prev parent reply other threads:[~2012-09-18 13:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 8:24 Error getting mfn William Dauchy
2012-09-18 13:36 ` Konrad Rzeszutek Wilk [this message]
2012-09-19 13:51 ` William Dauchy
2012-09-19 20:01 ` Konrad Rzeszutek Wilk
2012-09-20 13:29 ` William Dauchy
2012-09-20 13:48 ` Konrad Rzeszutek Wilk
2012-09-20 14:15 ` William Dauchy
2012-09-20 16:23 ` Pasi Kärkkäinen
2012-09-20 16:30 ` William Dauchy
2012-09-20 16:35 ` Pasi Kärkkäinen
2012-09-20 17:08 ` William Dauchy
2012-09-20 21:28 ` Konrad Rzeszutek Wilk
2012-09-23 15:11 ` William Dauchy
2012-09-25 8:40 ` William Dauchy
2012-09-25 21:36 ` Konrad Rzeszutek Wilk
2012-09-25 21:41 ` Konrad Rzeszutek Wilk
2012-10-05 14:06 ` William Dauchy
2012-09-18 18:50 ` Andrew Cooper
2012-09-19 13:52 ` William Dauchy
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=20120918133650.GC12053@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=wdauchy@gmail.com \
--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.