From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: 2.6.29-rc7 pv_ops dom0 BUG / unable to handle kernel paging request Date: Wed, 11 Mar 2009 16:40:24 -0700 Message-ID: <49B84BE8.4020103@goop.org> References: <20090307175856.GL15052@edu.joroinen.fi> <49B3610C.2090101@goop.org> <20090308115400.GR15052@edu.joroinen.fi> <20090311205250.GJ15052@edu.joroinen.fi> <20090311212622.GK15052@edu.joroinen.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090311212622.GK15052@edu.joroinen.fi> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Pasi K=E4rkk=E4inen wrote: > On Wed, Mar 11, 2009 at 10:52:50PM +0200, Pasi K=E4rkk=E4inen wrote: > =20 >> On Sun, Mar 08, 2009 at 01:54:01PM +0200, Pasi K=E4rkk=E4inen wrote: >> =20 >>> On Sat, Mar 07, 2009 at 10:09:16PM -0800, Jeremy Fitzhardinge wrote: >>> =20 >>>> Pasi K=E4rkk=E4inen wrote: >>>> =20 >>>>> Hello! >>>>> >>>>> Latest git tree (updated some hours ago) boots up fine for me, xend= can be=20 >>>>> started etc, but some time after starting kernel compilation I get = the=20 >>>>> following BUG: >>>>> >>>>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-= 19-xen331-linux-2.6.29-rc7-bug.txt >>>>> >>>>> (XEN) mm.c:2006:d0 Bad type (saw 28000001 !=3D exp e0000000) for mf= n 436a3=20 >>>>> (pfn 3d0a3) >>>>> (XEN) mm.c:707:d0 Error getting mfn 436a3 (pfn 3d0a3) from L1 entry= =20 >>>>> 00000000436a3063 for dom0 >>>>> (XEN) mm.c:3640:d0 ptwr_emulate: could not get_page_from_l1e() >>>>> BUG: unable to handle kernel paging request at c01cbd58 >>>>> IP: [] xen_set_pte+0x8c/0x96 >>>>> =20 >>>>> =20 >>>> Well, that's bad news. It was trying to map a highmem pte page whic= h=20 >>>> didn't have the Pinned bit set on its page, but Xen thought it was a= =20 >>>> pinned pte page. Not sure how it could get into that state, but its= =20 >>>> indicative of general memory corruption. >>>> >>>> What was going on at the time? Was dom0 busy? Were you running som= e domUs? >>>> >>>> =20 >>> At that time I was compiling a kernel on dom0.. so dom0 was busy. >>> >>> No other domains running.=20 >>> >>> =20 >> Same thing happened again.. with the latest tree (as of today). >> >> Again I was compiling a kernel in dom0, so dom0 was busy. No other dom= ains >> running.=20 >> >> =20 > > The exact same kernel booted on baremetal without Xen works OK, and doe= sn't > BUG during kernel compilation.=20 > > =20 That's good to know as a baseline, though the bug is Xen refusing to do=20 a pte update, so I'd be surprised if it happened with Xen in the picture = ;) What happens if you disable CONFIG_HIGHPTE? J