WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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: Teck Choon Giam <giamteckchoon@xxxxxxxxx>
Date: Wed, 9 Mar 2011 04:20:35 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Fajar A. Nugraha" <list@xxxxxxxxx>
Delivery-date: Tue, 08 Mar 2011 12:22:24 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fK4b2wi6ZzgDZSKvdwBtD6CBNB/ofNWT9aESeD2tEC8=; b=RAV6+saBoXqdH+qmTTPC9B5XsQ5KeGXD4BN6W1ceJ/KQIDudM56Vd39DRLMSjT1z3v nJLknm/rmN1ru7bxn2s0ujVvkZ6yH91mARj+05i6dM4X0mYVPgqt1B5I/LSpMvk1Puc+ O0NgdynS+Q+fQUaBu/Jwgyll+7QNmM0I9Dwd0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Q/NDSq6WEWuCflDtK9CEUXUXljo6MndB7UBphOUzYc65O6TdHn4TJ2i1GRP++nMwbU ImbSu9DpqFbha8wFu+fW7HRn/zEH2+2RgE2jYa6Xe6/AWiCJxHBGatOrLWhTrGaOucLf JNc9J8uuxSu51rvfz9IBfGkXwn36avM/vaWwY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110308201002.GA5721@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: <20110127203218.GB4194@xxxxxxxxxxxx> <AANLkTinZZC-oGoJ85tnFSLMs9xDEC2PndkrzLB_gseO5@xxxxxxxxxxxxxx> <AANLkTi=p7aCFAC448fgDC46chMSr6Fm7=FsPqDkL23Jy@xxxxxxxxxxxxxx> <20110228162023.GA11720@xxxxxxxxxxxx> <AANLkTikYnh0xbHLtyAR71FAOT18+g6SPxo25CGz5gKwh@xxxxxxxxxxxxxx> <20110303221639.GB12175@xxxxxxxxxxxx> <AANLkTi=r+ErO+PkPWF=3L8+v9+TPbgVz-6qaycTgMo4c@xxxxxxxxxxxxxx> <AANLkTimTuXqoLe9VinpAdhwJPO3Z8HGU2+KOoHOBaUvq@xxxxxxxxxxxxxx> <AANLkTimin0OZZUmvUr2KcXugc_2GGuEhRHLdug1ufha6@xxxxxxxxxxxxxx> <20110308192950.GA4562@xxxxxxxxxxxx> <20110308201002.GA5721@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On Wed, Mar 9, 2011 at 4:10 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
On Tue, Mar 08, 2011 at 02:29:50PM -0500, Konrad Rzeszutek Wilk wrote:
> > Yes.  All are set in my kernel config and I believed Konrad has my kernel
> > config.  I didn't use nomodeset as my servers don't have those graphic
> > cards... ...
>
> I am having a hard-time reproducing this. I made six LV's:

Aha!

respawning too fast: disabled for 5 minutes
INIT: Id "co" respawning too fast: disabled for 5 minutes
INIT: Id "co" respawning too fast: disabled for 5 minutes
INIT: Id "co" respawning too fast: disabled for 5 minutes
(XEN) mm.c:2364:d0 Bad type (saw 7400000000000001 != exp 3000000000000000) for mfn 354e0 (pfn c76d7)
(XEN) mm.c:942:d0 Attempt : entry 255
(XEN) mm.c:2117:d0 Error while validating mfn 35620 (pfn c7417) for type 4000000000000000: caf=8000000000000003 taf=4000000000000001
(XEN) mm.c:2733:d0 Error while pinning mfn 35620
(XEN) mm.c:2364:d0 Bad type (saw 7400000000000001 != exp 3000000000000000) for mfn 354e0 (pfn c76d7)
(XEN) mm.c:942:d0 Attempt to create linear p.t. with write perms
(XEN) mm.c:1487:d0 Failure in alloc_l4_table: entry 255
(XEN) mm.c:2117:d0 Error while validating mfn 3b286 (pfn c187d) for type 4000000000000000: caf=8000000000000003 taf=4000000000000001
(XEN) mm.c:2733:d0 Error while pinning mfn 3b286
(XEN) mm.c:2364:d0 Bad type (saw 7400000000000001 != exp 3000000000000000) for mfn 354e0 (pfn c76d7)
(XEN) mm.c:942:d0 Attempt to create linear p.t. with write perms
(XEN) mm.c:1487:d0 Failure in alloc_l4_table: entry 255
(XEN) mm.c:2117:d0 Error while validating mfn 35620 (pfn c7417) for type 4000000000000000: caf=8000000000000003 taf=4000000000000001
(XEN) mm.c:2500:d0 Error while installing new baseptr 35620
(XEN) mm.c:2364:d0 Bad type (saw 7400000000000001 != exp 3000000000000000) for mfn 354e0 (pfn c76d7)
(XEN) mm.c:942:d0 Attempt to create linear p.t. with write perms
(XEN) mm.c:1487:d0 Failure in alloc_l4_table: entry 255
(XEN) mm.c:2117:d0 Error while validating mfn 3b286 (pfn c187d) for type 4000000000000000: caf=8000000000000003 taf=4000000000000001
(XEN) mm.c:2825:d0 Error while installing new mfn 3b286
(XEN) mm.c:2794:d0 Mfn 35620 not pinned
(XEN) mm.c:2794:d0 Mfn 3b286 not pinned

Takes a bit of time to reproduce it, but I can reproduce it on my CentOS 5.5 OS.

Yep... it takes sometime to hit this bug and if you run my test script without any guest running will be faster to reproduce it.

May I know what is your normal development platform/distribution for xen?  I hope this isn't just distribution specific issue for PVOPS stable/xen-2.6.32.x Dom0... ... mostly not as from this thread alone I see someone saying they hit this bug as well and I believe they are not running CentOS 5.x... guess is debian based distribution.

Thanks.

Kindest regards,
Giam Teck Choon

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel