Re: [Xen-devel] Re: 2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap

[Jeremy Fitzhardinge <jeremy@xxxxxxxx>]

Guillaume Rousse wrote:
> Jeremy Fitzhardinge a écrit :
> > > FWIW, I just tried 2.6.26-rc1 and it booted fine.  I can narrow it 
> > > down further if that'd be useful to you.
> > >   
> > Yes, please.
> Was there any final conclusion there ? Because I'm currently trying a 
> 2.6.27.5 with the same kind of issue:
I don't know of any outstanding bugs which cause this kind of symptom.  
What's happening on the Linux side when the domain crashes this way?
   J

> (XEN) mm.c:1482:d31 Bad L1 flags 800000
> (XEN) traps.c:437:d31 Unhandled invalid opcode fault/trap [#6] on VCPU 
> 0 [ec=0000]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 31 (vcpu#0) crashed on cpu#2:
> (XEN) ----[ Xen-3.3.0  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    2
> (XEN) RIP:    e033:[<ffffffff8020b3ed>]
> (XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
> (XEN) rax: 00000000ffffffea   rbx: 000000000000077f   rcx: 
> 0000000000000054
> (XEN) rdx: 0000000000000000   rsi: 8000000331df5061   rdi: 
> ffffffff8077f000
> (XEN) rbp: ffffffff806e1f88   rsp: ffffffff806e1f28   r8:  
> 0000000000000010
> (XEN) r9:  0000000000000010   r10: ffffffff806e1e88   r11: 
> ffffffff80827f60
> (XEN) r12: ffffffff8077f000   r13: 8000000000000161   r14: 
> 8000000331df5061
> (XEN) r15: 0000000000000800   cr0: 000000008005003b   cr4: 
> 00000000000026b0
> (XEN) cr3: 000000033c35c000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
> (XEN) Guest stack trace from rsp=ffffffff806e1f28:
> (XEN)    0000000000000054 ffffffff80827f60 ffffffff8020b3ed 
> 000000010000e030
> (XEN)    0000000000010082 ffffffff806e1f68 000000000000e02b 
> ffffffff8020b3e9
> (XEN)    0000000000000200 000000000000000c 000000000000000c 
> 0000000000001800
> (XEN)    ffffffff806e1ff8 ffffffff806f99cf 0000000000000000 
> 0000000000001000
> (XEN)    0000000000001800 ffffffff80e48000 0000000000020000 
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 
> ffffffff80d45000
> (XEN)    ffffffff80d46000 ffffffff80d47000 ffffffff80d48000 
> ffffffff80d49000
> (XEN)    ffffffff80d4a000 ffffffff80d4b000 ffffffff80d4c000 
> ffffffff80d4d000
> (XEN)    ffffffff80d4e000 ffffffff80d4f000 ffffffff80d50000 
> ffffffff80d51000
> (XEN)    ffffffff80d52000 ffffffff80d53000 ffffffff80d54000 
> ffffffff80d55000
> (XEN)    ffffffff80d56000 ffffffff80d57000 ffffffff80d58000 
> ffffffff80d59000
> (XEN)    ffffffff80d5a000 ffffffff80d5b000 ffffffff80d5c000 
> ffffffff80d5d000
> (XEN)    ffffffff80d5e000 ffffffff80d5f000 ffffffff80d60000 
> ffffffff80d61000
> (XEN)    ffffffff80d62000 ffffffff80d63000 ffffffff80d64000 
> ffffffff80d65000
> (XEN)    ffffffff80d66000 ffffffff80d67000 ffffffff80d68000 
> ffffffff80d69000
> (XEN)    ffffffff80d6a000 ffffffff80d6b000 ffffffff80d6c000 
> ffffffff80d6d000
> (XEN)    ffffffff80d6e000 ffffffff80d6f000 ffffffff80d70000 
> ffffffff80d71000
> (XEN)    ffffffff80d72000 ffffffff80d73000 ffffffff80d74000 
> ffffffff80d75000
> (XEN)    ffffffff80d76000 ffffffff80d77000 ffffffff80d78000 
> ffffffff80d79000

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