From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: kernel BUG at arch/x86/xen/mmu.c:1860!
Date: Thu, 3 Mar 2011 17:16:39 -0500
Message-ID: <20110303221639.GB12175@dumpdata.com>
References: <20110124143615.GD6511@dumpdata.com>
	<AANLkTikdQ1KXe_oxaE9nRG=idq0zG3TV90NSjq1vdtZa@mail.gmail.com>
	<20110125144809.GA7405@dumpdata.com>
	<20110126143103.GB18978@dumpdata.com>
	<AANLkTimPihAQ7Qsh7ViQVEgNP0hbTRhiXsU42N+3ROcc@mail.gmail.com>
	<20110127203218.GB4194@dumpdata.com>
	<AANLkTinZZC-oGoJ85tnFSLMs9xDEC2PndkrzLB_gseO5@mail.gmail.com>
	<AANLkTi=p7aCFAC448fgDC46chMSr6Fm7=FsPqDkL23Jy@mail.gmail.com>
	<20110228162023.GA11720@dumpdata.com>
	<AANLkTikYnh0xbHLtyAR71FAOT18+g6SPxo25CGz5gKwh@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <AANLkTikYnh0xbHLtyAR71FAOT18+g6SPxo25CGz5gKwh@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Teck Choon Giam <giamteckchoon@gmail.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Tue, Mar 01, 2011 at 05:59:54PM +0800, Teck Choon Giam wrote:
> On Tue, Mar 1, 2011 at 12:20 AM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
> 
> > > This is just an update from my testing.
> > >
> > > I tried with latest xen/next-2.6.32.x and same bug still there:
> >
> > Grrrrrrrr..
> >
> > Let me setup a machine to reproduce this. Is the distro you are using
> > still CentOS 5?
> >
> 
> Yes.

OK, I got a machine with CentOS 5.5 installed. Had some trouble getting
the kernel to boot - a different issue that the one you are seeing however.

What arguments are you using for your dom0 and Xen hypervisor?