From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge 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 Message-ID: <4AF8B1E8.5080607@goop.org> References: <481249.38422.qm@web25602.mail.ukl.yahoo.com> <4A78CA69.3090105@goop.org> <0E87C0E865217944860BB378D2898000E1467F@srv-mail.apnos.int> <0E87C0E865217944860BB378D2898000E146B1@srv-mail.apnos.int> <4A7B306D.5080108@goop.org> <20091109235051.GA20408@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20091109235051.GA20408@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Olivier NOEL , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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