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:10:17 +0100
Cc: Teck Choon Giam <giamteckchoon@xxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Tue, 04 Jan 2011 07:10:48 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=saout.de; s=default; t=1294153796; bh=J8luyygyL/kUD8KGL7kdVebPsPoSrsVoUuEUtl9WyE4=; h=Subject:From:In-Reply-To:References:Date:Message-ID; b=UK306w3mswKk43tvxA0a6HlthAiy7+gPzNobGU+NIrrpDrhEByTfybIxIzEJ6Korp Xdp1H7qACw2W4e1r4gp8LpSdd6kk0qnA+toFGTkMzae2KjDHTOAPHucrruXBGuRRJ4 F4q4rchyMoFssmUNtUZZQ+lwsB/CZfvG/3gS/wew=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101228104256.GJ2754@xxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello thread,

hijacking this thread since I am running into the same issue on a new

> >      > 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...


Xen-devel mailing list