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 09:42:02 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 23 Jan 2011 17:43:05 -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=ytPqjwj24EL1xEWxSDBjmT0+910YruUShTT1h9bFeLU=; b=AvTbH+gktz10TB6yGP427Qkh5cjwwMd+Mr6Gf54nLz3Wrw8m9ZQCXNf6wlRCBwgcDd A4F4nsYbmnwV3l9NYPV58QeLBiWh6YZTi6k9MaQ5gKzUYXH7QaAatj3FFldwHAUXr4ld Yqk9y21OqmkOX0nuqIz9hD5y9zTFyLA5U1UfE=
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=hLTDUwHI5Vel0mOPGrT8z6/2w566NgPcNPBISZvv6QR2mCl6Q9XjtJyrCEtR0tk/Bg GIstpVDywCH9w3PFHhpe1sthZyGR5SyeiCJQnbXqCRjX7n1TTcXPGw1SXFfW6gM39OnS ZWF+FZEexeOJXWaGI2q1Q7e4WlDd/MGoakuJY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTimtC4HADFmQy-kDxRC4tX0sTQ=B7Xayh8moCjXv@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: <AANLkTi=Hwjooo43FiLPAAGzzOTG440ij_QsEqks6ECVv@xxxxxxxxxxxxxx> <20101227155314.GG3728@xxxxxxxxxxxx> <AANLkTikNvKGc78HQOMtVfi=Q+r8r92=svzZcMLQ2xojQ@xxxxxxxxxxxxxx> <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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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 :(

Thanks.

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