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: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] kernel BUG at arch/x86/xen/mmu.c:1860!
From: Christophe Saout <christophe@xxxxxxxx>
Date: Fri, 14 Jan 2011 16:33:52 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Teck Choon Giam <giamteckchoon@xxxxxxxxx>
Delivery-date: Fri, 14 Jan 2011 07:34:13 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=saout.de; s=default; t=1295019214; bh=Z/6PTnLCMK8NWur28ozwLpcesoGHZD5Y1t0b5jNlCuU=; h=Subject:From:In-Reply-To:References:Date:Message-ID; b=Uo/3m7CgRgHHENin/j1xjsH7pDiV+UgcanvQk8Jkk+UwDPoAv098bX0XtRxjqYyGL HGAHReArUNd9IaL6YSlTxsy7BnO6ojb0WGV92vjfGmBzlswIQE+jFCwNdPN53jwcP6 hnKhRT5lwWsPEBSn/DL5TvAaHpi+vCfmfbZO9hM8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110114152217.GB7455@xxxxxxxxxxxx>
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> <1294154342.24719.6.camel@xxxxxxxxxxxxxxxxxxxx> <1294166410.24719.11.camel@xxxxxxxxxxxxxxxxxxxx> <20110114152217.GB7455@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Konrad,

> > (without strace, the bug is very common, about every third "lvcreate"
> > command.  Every lvcreate command triggers about 20 multipath
> Something must be busted with your udev rules for this to go in effect.
> You should have multipathd process those and not run multipath for
> every device mapper call.

This is a standard Debian squeeze.  I think udev is just calling those
to figure out if a device should be handled by multipath or not (part of
the device identification). I'd rather not fiddle with it, as it "works"
even if Debian is shipping suboptimal rules. Anyhow, changing this would
simply reduce the risk of running into the kernel issue, not remove it
entirely, so I prefer the actual fix. :)


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>