From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Olivier NOEL <ONOEL@tetra-info.com>, xen-devel@lists.xensource.com
Subject: Re: mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a
Date: Mon, 09 Nov 2009 16:20:56 -0800 [thread overview]
Message-ID: <4AF8B1E8.5080607@goop.org> (raw)
In-Reply-To: <20091109235051.GA20408@phenom.dumpdata.com>
On 11/09/09 15:50, Konrad Rzeszutek Wilk wrote:
>>> (XEN) mm.c:645:d50 Non-privileged (50) attempt to map I/O space 00000000
>>> (XEN) mm.c:645:d51 Non-privileged (51) attempt to map I/O space 00000000
>>>
> I can get this with the most recent kernel when PV and QEMU are involved.
> But _not_ if only PV is booted and QEMU is not present.
>
I'm sorry to say that I'd noticed this myself and quietly ignored it
hoping someone else would root-cause it ;)
It appears to be something wrong with the xenfb driver's mapping which
Xen is complaining about, but I hadn't got further than that.
J
next prev parent reply other threads:[~2009-11-10 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 9:44 kernel BUG at arch/x86/xen/multicalls.c:103! Olivier NOEL
2009-08-04 23:55 ` Jeremy Fitzhardinge
2009-08-05 7:10 ` Olivier NOEL
2009-08-06 6:50 ` Olivier NOEL
2009-08-06 19:35 ` Jeremy Fitzhardinge
2009-11-09 23:50 ` mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a Konrad Rzeszutek Wilk
2009-11-10 0:20 ` Jeremy Fitzhardinge [this message]
2009-12-01 3:11 ` mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a + (XEN) mm.c:845:d20 Error getting mfn jd (pfn 84fd) from L1 entry 800000000246d467 for l1e_owner=20, pg_owner=32753 Konrad Rzeszutek Wilk
2009-12-01 6:40 ` Jeremy Fitzhardinge
2009-12-01 21:57 ` Konrad Rzeszutek Wilk
2009-12-01 22:44 ` Jeremy Fitzhardinge
2009-12-01 23:05 ` Konrad Rzeszutek Wilk
2009-12-01 9:26 ` Markus Armbruster
2009-12-01 16:14 ` Konrad Rzeszutek Wilk
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=4AF8B1E8.5080607@goop.org \
--to=jeremy@goop.org \
--cc=ONOEL@tetra-info.com \
--cc=konrad.wilk@oracle.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.