xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Kathy Hadley <Kathy.Hadley@dornerworks.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
Date: Tue, 22 Jun 2010 20:16:29 +0100	[thread overview]
Message-ID: <C846CA9D.18410%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <D3E384327F5C6D48AADCEA84160B7D73014714A7@mcbain.dw.local>

On 22/06/2010 20:10, "Kathy Hadley" <Kathy.Hadley@dornerworks.com> wrote:

> Looking at the output to the serial channel, I see the following message
> (which was not output on an earlier version of Xen [xen-unstable downloaded
> May 27] where I can successfully start other domains):
> 
> (XEN) traps.c:2301:d2 Domain attempted WRMSR c0000080 from 0x0000080000000000
> to 0x0000080000000800.
> 
> Would this explain why the new domain appears to hang?

I think it might be a side effect of some MSR cleanup patches in the
hypervisor, and pribably not related to your hang. You'll need to track down
where your guest kernel is hanging. Add some early printks or maybe use the
xenctx tool to get an EIP value and map that to a location in the kernel
code.

 -- Keir

  reply	other threads:[~2010-06-22 19:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 15:04 [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools) Kathy Hadley
2010-06-16 15:50 ` George Dunlap
2010-06-16 16:00   ` Kathy Hadley
2010-06-16 16:13     ` Keir Fraser
2010-06-16 16:14     ` George Dunlap
2010-06-16 16:20       ` Keir Fraser
2010-06-16 16:25         ` Kathy Hadley
2010-06-16 16:31           ` Keir Fraser
2010-06-16 16:40             ` Kathy Hadley
2010-06-16 16:49               ` Keir Fraser
2010-06-16 18:03                 ` Kathy Hadley
2010-06-17  7:04                   ` Keir Fraser
2010-06-17 18:16                     ` Kathy Hadley
2010-06-17 18:26                       ` Keir Fraser
2010-06-18 17:35                     ` Kathy Hadley
2010-06-18 17:49                       ` Keir Fraser
2010-06-19 11:14                       ` George Dunlap
2010-06-22 19:10                     ` Kathy Hadley
2010-06-22 19:16                       ` Keir Fraser [this message]
2010-06-23 19:57                         ` Kathy Hadley
2010-06-23 20:23                           ` Keir Fraser
2010-06-23 21:16                             ` Kathy Hadley
2010-06-23 22:36                               ` Keir Fraser
2010-06-24 12:53                                 ` Kathy Hadley
2010-06-24 13:08                                   ` Dan Magenheimer
2010-06-24 13:18                                     ` Kathy Hadley
2010-06-24 13:23                                     ` Keir Fraser
2010-06-24 13:32                                       ` Kathy Hadley
2010-06-30 20:44                                 ` Kathy Hadley
2010-06-30 20:54                                   ` Keir Fraser
2010-07-14 17:32                                     ` Kathy Hadley
2010-07-14 18:04                                       ` Keir Fraser
2010-06-16 16:25         ` George Dunlap
2010-06-17  5:02         ` Juergen Gross
2010-06-17  6:09           ` Keir Fraser

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=C846CA9D.18410%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Kathy.Hadley@dornerworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).