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: Mon, 24 Jan 2011 23:56:21 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 24 Jan 2011 07:57:18 -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=tKfBf3e+cgGTny5Ln2T6YcsMuhXVnnVCRef33Dtrbow=; b=AwmqvardhNFPEs3biff0E4AJDSutZ5qvOqMQBDIP3huK0OD1wdUUwSflFzaa4zrjhg aMRhtwLuhnLjXlyH+TkADQhgLTS5Kvr0iUTtWXW8+yu4cR/HNLFox/RVjIDeCdESEQrd tMVJZFKJmDJFhJQAfKWG9KM0tq8syPcrqPFAQ=
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=rsBp26WyvT1coMCZCKvAv/lN91IX+7aZkU2E+WhyR66ICWc03l5o5J6IjLsnUJDZgG omcGAO9qaM+S2iJVCEp6CBTFqyOl+A7776H48G5aMif96TPB3pBjeTIENI+caZ6J62rK UN+JdGXQQpaMq+JmsMlhG5dpMqj+otI1xAC+k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110124143615.GD6511@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: <20101228104256.GJ2754@xxxxxxxxxxx> <AANLkTin+B1LZLWeJ2z3ZN6AovDbdnmDg4crQkX66K53c@xxxxxxxxxxxxxx> <AANLkTin7A71hjbbDCVjvX6+q8yVGrg9dK4pesccNzQhh@xxxxxxxxxxxxxx> <AANLkTikusLNCrh3mqh7iZ_d4ftP94rc2HURiEp=WmwA6@xxxxxxxxxxxxxx> <20110114152039.GA7455@xxxxxxxxxxxx> <AANLkTiktYYo09o0kjfXTpmCu_O5G2va8PYbn_gz2Rg=J@xxxxxxxxxxxxxx> <20110114194437.GA25672@xxxxxxxxxxxx> <AANLkTine-4W4bAq5xGqB7C8RzhP_5LYz-S6HMRcWA67Y@xxxxxxxxxxxxxx> <AANLkTimtC4HADFmQy-kDxRC4tX0sTQ=B7Xayh8moCjXv@xxxxxxxxxxxxxx> <AANLkTimkLGmX47gMKXxFbGgCe3LMQOyvHRoRSfgT=stS@xxxxxxxxxxxxxx> <20110124143615.GD6511@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On Mon, Jan 24, 2011 at 10:36 PM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
On Mon, Jan 24, 2011 at 09:42:02AM +0800, Teck Choon Giam wrote:
> Sorry, does anyone able to solve this bug?  My prevention doing sleep 5 and
> sync method only last me longest 20+- days of uptime then the same bug will
> appear :(

You have to give more details. Which kernel and what does the back-trace look like?

Thanks for your prompt reply.

Kernel is from http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary latest stable/2.6.32.x

Xen version is from http://xenbits.xensource.com/staging/xen-4.0-testing.hg latest changeset 21439 in fact any changeset 214xx I believe.

I have posted console output for one of my xen servers and maybe my serial console configuration not right... ...

http://lists.xensource.com/archives/html/xen-devel/2011-01/msg00177.html

How do I back-trace?  You mean I should execute my test crash script with strace and post the output during crash?

Thanks.

Kindest regards,
Giam Teck Choon
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel