RE: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)

["Kathy Hadley" <Kathy.Hadley@xxxxxxxxxxxxxxx>]

Keir,
  Thanks for the suggestions.  When I use the xenctx tool, I see the
following:

cs:eip: 0061:c01013a7 hypercall_page+0x3a7 
flags: 00001246 i z p
ss:esp: 0069:c03fff90
eax: 00000000    ebx: deadbeef    ecx: deadbeef    edx: 00000001
esi: 00000000    edi: c0433180    ebp: 00000000
 ds:     007b     es:     007b     fs:     0000     gs:     0000
Code (instr addr c01013a7)
cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 cd 82 <c3> cc
cc cc cc cc cc cc cc cc cc 


Stack:
 c0109005 f9d66eef 0000035d 00000000 ffffffff c0433100 c0104789 c010482d
 00000000 00000020 00000020 c04369e4 c12148e4 c1211000 c0404895 c033b1d0
 c04041d0 00000000 3fbccf00 00000e39 00008000 000038e4 c043aaa0 00020800
 c04e5000 00000000 00000000 00000000

Call Trace:
  [<c01013a7>] hypercall_page+0x3a7  <--
  [<c0109005>] raw_safe_halt+0xa5 
  [<c0104789>] xen_idle+0x49 
  [<c010482d>] cpu_idle+0x8d 
  [<c0404895>] start_kernel+0x3f5 
  [<c04041d0>] do_early_param+0x80

  Does this shed any light on the situation?

  Thanks,
Kathy Hadley

> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Tuesday, June 22, 2010 3:16 PM
> To: Kathy Hadley; George Dunlap
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated
> to add support for CPU pools)
> 
> On 22/06/2010 20:10, "Kathy Hadley" <Kathy.Hadley@xxxxxxxxxxxxxxx>
> 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
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel