[Xen-devel] RE: kernel panic when enable x2apic

["Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>]

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx]
> Sent: Wednesday, November 17, 2010 5:42 PM
> To: Zhang, Yang Z
> Cc: Han, Weidong; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: kernel panic when enable x2apic
> 
> >>> On 17.11.10 at 09:59, "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx> wrote:
> > Did your test your patch with x2apic enabled? We always see kernel panic
> 
> No, due to there not being a suitable box accessible to me.
> 
> > when enable x2apic since 22375? And without your patch or set x2apic=0 in
> xen
> > command line, it works fine.
> > Any suggestions?
> 
> Not immediately.
> 
> > (XEN) ----[ Xen-4.1-unstable  x86_64  debug=y  Tainted:    C ]----
> > (XEN) CPU:    0
> > (XEN) RIP:    e008:[<ffff82c48013cac9>]
> pci_get_pdev_by_domain+0x49/0x5b
> > (XEN) RFLAGS: 0000000000010207   CONTEXT: hypervisor
> > (XEN) rax: 0000000000000000   rbx: ffff83007f034000   rcx:
> 0000000000000000
> > (XEN) rdx: 00000000ffffffff   rsi: 00000000ffffffff   rdi: ffff83007f034000
> > (XEN) rbp: ffff82c480297d38   rsp: ffff82c480297d38   r8:
> 0000000000000000
> > (XEN) r9:  ffff82c4802525b0   r10: 0000000000000000   r11:
> 0000000000000000
> > (XEN) r12: ffff83007f034000   r13: 0000000000000004   r14:
> 0000000000000000
> > (XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4:
> 00000000000026f0
> > (XEN) cr3: 000000007f29c000   cr2: 0000000000000000
> > (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> > (XEN) Xen stack trace from rsp=ffff82c480297d38:
> > (XEN)    ffff82c480297d78 ffff82c48013cec5 ffff82c480297d58
> ffff83007f034000
> > (XEN)    ffff83007f034000 0000000000000004 0000000000000000
> 0000000000000000
> > (XEN)    ffff82c480297d98 ffff82c480152fd4 ffff83007f034000
> 000000000000003f
> > (XEN)    ffff82c480297dd8 ffff82c480104e1d ffff82c48028a298
> 0000000000000080
> > (XEN)    0000000000000080 0000000000000007 0000000000000008
> 0000000000000007
> > (XEN)    ffff82c480297f08 ffff82c48027802b 0000000000000000
> 0000000000000000
> > (XEN)    ffff82c4802596a5 0000000000259640 00f1400000000000
> 0000000000000000
> > (XEN)    ffff83000007bc50 ffff83000007bfb0 ffff83000007bef0
> 0000000000f14000
> > (XEN)    0000000000000000 0000000000000000 0000000020000000
> 0000000000000000
> > (XEN)    0000000000000000 ffffffffffffffff ffff83000007bef0
> 000000000007bef0
> > (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> > (XEN)    ffff82c480287cc8 0000000001000000 ffffffff00000000
> ffff82c480259640
> > (XEN)    0000000800000000 000000010000006e 0000000000000003
> 00000000000002f8
> > (XEN)    0000000000000000 0000000000000000 000000007c223900
> 000000007de55018
> > (XEN)    0000000000000000 0000000000000001 0000000000067ebc
> ffff82c4801000b5
> > (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> > (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> > (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> > (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> > (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> > (XEN) Xen call trace:
> > (XEN)    [<ffff82c48013cac9>] pci_get_pdev_by_domain+0x49/0x5b
> > (XEN)    [<ffff82c48013cec5>] pci_release_devices+0x200/0x230
> > (XEN)    [<ffff82c480152fd4>] arch_domain_destroy+0x28/0x2c9
> > (XEN)    [<ffff82c480104e1d>] domain_create+0x3cb/0x46e
> > (XEN)    [<ffff82c48027802b>] __start_xen+0x5660/0x5935
> 
> With arch_domain_destroy() on the call stack, things went wrong
> earlier (and the crash likely is in some error path, where I'd expect
> the problem has always existed, just that it was never hit). Was
> there no other relevant output prior to the actual crash?
> 

In fact, there have other error info before the crash and I didn't see it 
before:
(XEN) traps.c:2938: GPF (0000): ffff82c4801a0a73 -> ffff82c48020f0d2
(XEN) MTRR: CPU 0: Writing MSR 200 to ffff83007f0f7670 failed
(XEN) traps.c:2938: GPF (0000): ffff82c4801a0a73 -> ffff82c48020f0d2
(XEN) MTRR: CPU 0: Writing MSR 201 to f00000010 failed

best regards
yang
> Jan


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