This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] kernel BUG at arch/x86/xen/mmu.c:1860!

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] kernel BUG at arch/x86/xen/mmu.c:1860!
From: Christophe Saout <christophe@xxxxxxxx>
Date: Tue, 04 Jan 2011 16:19:02 +0100
Cc: Teck Choon Giam <giamteckchoon@xxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Tue, 04 Jan 2011 07:19:15 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=saout.de; s=default; t=1294154319; bh=ogWct6LJo/586klU0EGeGkn9onx5TBp0Xu/SJPqfH9s=; h=Subject:From:In-Reply-To:References:Date:Message-ID; b=ln+V2rZuJRhBCh48IOuBEEHiYJtPERExJWn+zVr+3WpEixnIEQIqtSGHPFAGYBgSV b0chlYwh0KS2eSrNwUwkiIXNVilw9jmbySgn84qGdmXdDkNQng8tv9/s5Ghp81JO9J a3tO7uEWrOZLtW00+44LsB+2e2/KbCabrOgoOGe8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1294153817.24719.3.camel@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTi=Hwjooo43FiLPAAGzzOTG440ij_QsEqks6ECVv@xxxxxxxxxxxxxx> <20101227155314.GG3728@xxxxxxxxxxxx> <AANLkTikNvKGc78HQOMtVfi=Q+r8r92=svzZcMLQ2xojQ@xxxxxxxxxxxxxx> <20101228104256.GJ2754@xxxxxxxxxxx> <1294153817.24719.3.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi again,

> > >      > While doing LVM snapshot for migration and get the following:
> > >      >
> > >      > Dec 26 15:58:29 xen01 kernel: ------------[ cut here ]------------
> > >      > Dec 26 15:58:29 xen01 kernel: kernel BUG at 
> > > arch/x86/xen/mmu.c:1860!
> > >      > Dec 26 15:58:29 xen01 kernel: invalid opcode: 0000 [#1] SMP
> > >      > Dec 26 15:58:29 xen01 kernel: last sysfs file: /sys/block/dm-26/dev
> > >      > Dec 26 15:58:29 xen01 kernel: CPU 0
> > >      > Dec 26 15:58:29 xen01 kernel: Modules linked in: ipt_MASQUERADE
> >
> > It would be very good to track this down and get it fixed.. 
> > hopefully you're able to help a bit and try some things to debug it.
> > 
> > Konrad maybe has some ideas to try.. 
> I am seeing this with an lvcreate here, so I guess it's somehow related
> to device-mapper stuff in general.
> It doesn't look like this has been resolved yet.  Somewhere I saw a
> request for the hypervisor message related to the pinning failure.
> Here it is:
> (XEN) mm.c:2364:d0 Bad type (saw 7400000000000001 != exp 1000000000000000) 
> for mfn 41114f (pfn d514f)
> (XEN) mm.c:2733:d0 Error while pinning mfn 41114f
> I have a bit of experience in debugging things, so if I can help someone
> with more information...

Additional information: This happened with a number of commands now.
However, I am running a multipath setup and every time the crash seemed
to be caused in the process context of the multipath daemon.  I think
the daemon listens to events from the device-mapper subsystem to watch
for changes and the problem somehow arises from there, since on another
machine with the same XEN/Dom0 version without such a daemon I never had
any troubles with LVM.

 [<ffffffff810052e2>] pin_pagetable_pfn+0x52/0x60    
 [<ffffffff81006f5c>] xen_alloc_ptpage+0x9c/0xa0
 [<ffffffff81006f8e>] xen_alloc_pte+0xe/0x10
 [<ffffffff810decde>] __pte_alloc+0x7e/0xf0
 [<ffffffff810e15c5>] handle_mm_fault+0x855/0x930
 [<ffffffff8102dd9e>] ? pvclock_clocksource_read+0x4e/0x100
 [<ffffffff810e734c>] ? do_mmap_pgoff+0x33c/0x380
 [<ffffffff81452b96>] do_page_fault+0x116/0x3e0
 [<ffffffff8144ff65>] page_fault+0x25/0x30


Xen-devel mailing list