[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] kernel BUG at arch/x86/xen/mmu.c:1860!


  • To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • From: Teck Choon Giam <giamteckchoon@xxxxxxxxx>
  • Date: Wed, 5 Jan 2011 03:24:27 +0800
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 04 Jan 2011 11:28:44 -0800
  • 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=gL+9gKorFIK+FuW4XNEEN4mr4d5De//V7V4WPR3qyQot9zRZFimxf2tYQ3bbkwrcFH RnOLX0tmsRk2USMRgbA5NhybZGI4jLFRO9sIk6LfObeajWKy3k/ji8mV22DX40ZdhLWr IcVEXBdC4idRSS5EKdCj4hApv+jn7MXPNYnQc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>



On Tue, Jan 4, 2011 at 9:48 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
On Sun, 2010-12-26 at 08:16 +0000, Teck Choon Giam wrote:
>
> Triggered BUG() in line 1860:
>
> static void pin_pagetable_pfn(unsigned cmd, unsigned long pfn)
> {
>         struct mmuext_op op;
>         op.cmd = cmd;
>         op.arg1.mfn = pfn_to_mfn(pfn);
>            if (HYPERVISOR_mmuext_op(&op, 1, NULL, DOMID_SELF))
>                    BUG(); <<THIS ONE?
> }

A failure to pin/unpin is usually associated with a log message from the
hypervisor. Please can you attempt to capture the full host log, e.g.
using serial console.

See http://wiki.xen.org/xenwiki/XenParavirtOps under "Are there more
debugging options I could enable to troubleshoot booting problems?" for
some details.

I will once I got the serial console cable and have a system to catch the log during my next visit to the DC.

Thanks.

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.