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: Teck Choon Giam <giamteckchoon@xxxxxxxxx>
Subject: Re: [Xen-devel] kernel BUG at arch/x86/xen/mmu.c:1860!
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 25 Jan 2011 09:48:09 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 25 Jan 2011 07:20:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikdQ1KXe_oxaE9nRG=idq0zG3TV90NSjq1vdtZa@xxxxxxxxxxxxxx>
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: <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> <AANLkTikdQ1KXe_oxaE9nRG=idq0zG3TV90NSjq1vdtZa@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Mon, Jan 24, 2011 at 11:56:21PM +0800, Teck Choon Giam wrote:
> 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.hglatest
> 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?


No that is OK. I now remember this one - I am poking at the code to get an idea
of what might be happening. No data yet.

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