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: Fri, 4 Mar 2011 13:30:08 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 03 Mar 2011 21:30:48 -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=XyYA8lXxDCcuORNUtVsUTG0B7U4GhLFq1FSRbCNzdTk=; b=omE/JqUWUdDwtoXh4xOrzg0xB40VDC2LDu9LnnzKVZbjalnoZu7/0pRLYRTwlPCkBZ 8tIFNXSf6IaGcyOHAWEIYSY9yWH91u+hAhAXMqHOm69HKcWddS4/6o+azUB1OU6B5u/E qZsszktYvbevKbdDmk0HbsawGx2QuRktB2iRY=
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=pciWEoPvrkVGJ6u0QfIh3tGntK+gy/sQH80zeQwY6Xe5fQj/pf5OJJyGM/KR4zFNoN CjlaeMmIua1nVqmGCRVduMUpqNIBk6E2O7YI5O/IZe/32fprKffiOfNi6hCBebcuNyx0 LTcR5Z1YktL8Wt60gNuGenSmith318Xr3W4cY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110303221639.GB12175@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: <20110124143615.GD6511@xxxxxxxxxxxx> <AANLkTikdQ1KXe_oxaE9nRG=idq0zG3TV90NSjq1vdtZa@xxxxxxxxxxxxxx> <20110125144809.GA7405@xxxxxxxxxxxx> <20110126143103.GB18978@xxxxxxxxxxxx> <AANLkTimPihAQ7Qsh7ViQVEgNP0hbTRhiXsU42N+3ROcc@xxxxxxxxxxxxxx> <20110127203218.GB4194@xxxxxxxxxxxx> <AANLkTinZZC-oGoJ85tnFSLMs9xDEC2PndkrzLB_gseO5@xxxxxxxxxxxxxx> <AANLkTi=p7aCFAC448fgDC46chMSr6Fm7=FsPqDkL23Jy@xxxxxxxxxxxxxx> <20110228162023.GA11720@xxxxxxxxxxxx> <AANLkTikYnh0xbHLtyAR71FAOT18+g6SPxo25CGz5gKwh@xxxxxxxxxxxxxx> <20110303221639.GB12175@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On Fri, Mar 4, 2011 at 6:16 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
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@xxxxxxxxxx> 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?


Example in one of my test server:

title CentOS (2.6.32.29-0.xen.pvops.choon.centos5)
    root (hd0,0)
    kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all cpuidle=0 cpufreq=none
    module /vmlinuz-2.6.32.29-0.xen.pvops.choon.centos5 ro root=/dev/md1 panic=5 panic_timeout=5
    module /initrd-2.6.32.29-0.xen.pvops.choon.centos5.img
 
Thanks.

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