From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: 2.6.32.27 dom0 + latest xen staging boot failure
Date: Fri, 28 Jan 2011 10:28:43 -0500 [thread overview]
Message-ID: <20110128152843.GB29440@dumpdata.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D53019438F211@orsmsx505.amr.corp.intel.com>
On Thu, Jan 27, 2011 at 10:51:42AM -0800, Kay, Allen M wrote:
> Following are the brief error messages from the serial console log. I have also attached the full serial console log and dom0 system map.
>
> (XEN) mm.c:802:d0 Bad L1 flags 400000
On a second look, this is a different issue than I had encountered.
The 400000 translates to Xen thinking you had PAGE_GNTTAB set, but that
is not right. Googling for this shows that I had fixed this with a
Xorg server at some point, but I can't remember the details so that is not
that useful :-(
You said it works if you give the domain 1024MB, but I wonder if
it also works if you disable the IOMMU? What happens then?
> (XEN) mm.c:1204:d0 Failure in alloc_l1_table: entry 90
> (XEN) mm.c:2142:d0 Error while validating mfn 1d7e97 (pfn 3d69) for type 1000000
> 000000000: caf=8000000000000003 taf=1000000000000001
> (XEN) mm.c:2965:d0 Error while pinning mfn 1d7e97
> (XEN) traps.c:451:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000
> ]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
next prev parent reply other threads:[~2011-01-28 15:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 2:26 2.6.32.27 dom0 + latest xen staging boot failure Kay, Allen M
2011-01-25 14:39 ` Konrad Rzeszutek Wilk
2011-01-25 18:49 ` Kay, Allen M
2011-01-25 19:07 ` Konrad Rzeszutek Wilk
2011-01-25 19:24 ` Kay, Allen M
2011-01-25 20:10 ` Konrad Rzeszutek Wilk
2011-01-25 21:26 ` Kay, Allen M
2011-01-26 2:41 ` Kay, Allen M
2011-01-26 16:14 ` Konrad Rzeszutek Wilk
2011-01-26 18:46 ` Kay, Allen M
2011-01-26 21:28 ` Konrad Rzeszutek Wilk
2011-01-26 21:53 ` Kay, Allen M
2011-01-27 1:16 ` Kay, Allen M
2011-01-27 11:59 ` Stefano Stabellini
2011-01-27 18:51 ` Kay, Allen M
2011-01-28 15:28 ` Konrad Rzeszutek Wilk [this message]
2011-01-28 15:47 ` Konrad Rzeszutek Wilk
2011-02-11 1:03 ` Kay, Allen M
2011-02-11 2:56 ` Jeremy Fitzhardinge
2011-02-11 3:07 ` Kay, Allen M
2011-02-11 17:06 ` Jeremy Fitzhardinge
2011-02-11 19:00 ` Kay, Allen M
2011-02-11 19:11 ` Kay, Allen M
2011-02-11 22:55 ` Jeremy Fitzhardinge
2011-02-15 4:28 ` Kay, Allen M
2011-02-15 14:58 ` Stefano Stabellini
2011-02-16 3:08 ` Kay, Allen M
2011-02-16 17:19 ` Stefano Stabellini
2011-02-11 14:51 ` Stefano Stabellini
2011-02-11 22:10 ` Kay, Allen M
2011-01-27 14:45 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110128152843.GB29440@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=allen.m.kay@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.