Kay, Allen M
2009-May-30 00:08 UTC
[Xen-devel] cs #19650 caused system panic when boot guest with passthrough device
I got the following system panic when I passthrough a PCI device using the latest xen-unstable tree. I have narrowed it down to cs #19650: eliminate hard-coded NR_IRQS. (XEN) ----[ Xen-3.4.0-rc4-pre x86_64 debug=n Not tainted ]---- (XEN) CPU: 15 (XEN) RIP: e008:[<ffff828c8013c391>] __find_next_bit+0x21/0x70 (XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor (XEN) rax: 0000000000000000 rbx: 0000000000000038 rcx: 0000000000000038 (XEN) rdx: 0000000000000038 rsi: 0000000000000038 rdi: ff7f83007a376fe0 (XEN) rbp: ffff83007cc169f0 rsp: ffff83007d78fe60 r8: 0000000000000061 (XEN) r9: 00000000000000fc r10: 0000000000000830 r11: 0000000000000020 (XEN) r12: 0000000000000037 r13: ffff830000f80010 r14: 0000000000000898 (XEN) r15: ffff83007a2c4000 cr0: 000000008005003b cr4: 00000000000026f0 (XEN) cr3: 000000007a365000 cr2: 0000000000c42c5c (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) Xen stack trace from rsp=ffff83007d78fe60: (XEN) ffff83007cc16150 ffff83007cc169f0 ffff828c8012f8e5 0000000001c9c380 (XEN) ffff830000f80438 ffff830000f80438 ffff83007a2c4178 0000000000000037 (XEN) ffff83007cc28000 ffff83007cc28000 ffff83007d796000 0000000000000000 (XEN) 0000000000004016 ffff828c80243100 ffff828c8019b9aa ffff828c801188a8 (XEN) ffff83007d78ff28 ffff83007d78ff28 ffff828c80286900 ffff83007cc28000 (XEN) ffff83007cc28000 ffff83007d796000 0000001c8063eb1f 0000000000000000 (XEN) ffff828c8019b778 0000000000000000 ffffffff80590f00 ffffffffffffffff (XEN) 0000000000000000 0000000000093380 00000003a2498219 0000000000000000 (XEN) 0000000000000001 00000000ffffffff 0000000000093380 00000003a2498219 (XEN) 00000003a2498219 000000000000000f 000000002437ac19 ffffffff80561f48 (XEN) 000000f000000000 ffffffff8020adb0 0000000000000000 0000000000000296 (XEN) ffffffff80561f68 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 000000000000000f ffff83007cc28000 (XEN) Xen call trace: (XEN) [<ffff828c8013c391>] __find_next_bit+0x21/0x70 (XEN) [<ffff828c8012f8e5>] hvm_dirq_assist+0xa5/0x2d0 (XEN) [<ffff828c8019b9aa>] vmx_intr_assist+0x5a/0x220 (XEN) [<ffff828c801188a8>] do_softirq+0x58/0x80 (XEN) [<ffff828c8019b778>] vmx_asm_do_vmentry+0x5/0xdd (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 15: (XEN) GENERAL PROTECTION FAULT (XEN) [error_code=0000] (XEN) **************************************** _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2009-May-30 09:25 UTC
Re: [Xen-devel] cs #19650 caused system panic when boot guest with passthrough device
Hopefully fixed by c/s 19682. -- Keir On 30/05/2009 01:08, "Kay, Allen M" <allen.m.kay@intel.com> wrote:> I got the following system panic when I passthrough a PCI device using the > latest xen-unstable tree. I have narrowed it down to cs #19650: eliminate > hard-coded NR_IRQS. > > (XEN) ----[ Xen-3.4.0-rc4-pre x86_64 debug=n Not tainted ]---- > (XEN) CPU: 15 > (XEN) RIP: e008:[<ffff828c8013c391>] __find_next_bit+0x21/0x70 > (XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor > (XEN) rax: 0000000000000000 rbx: 0000000000000038 rcx: 0000000000000038 > (XEN) rdx: 0000000000000038 rsi: 0000000000000038 rdi: ff7f83007a376fe0 > (XEN) rbp: ffff83007cc169f0 rsp: ffff83007d78fe60 r8: 0000000000000061 > (XEN) r9: 00000000000000fc r10: 0000000000000830 r11: 0000000000000020 > (XEN) r12: 0000000000000037 r13: ffff830000f80010 r14: 0000000000000898 > (XEN) r15: ffff83007a2c4000 cr0: 000000008005003b cr4: 00000000000026f0 > (XEN) cr3: 000000007a365000 cr2: 0000000000c42c5c > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008 > (XEN) Xen stack trace from rsp=ffff83007d78fe60: > (XEN) ffff83007cc16150 ffff83007cc169f0 ffff828c8012f8e5 0000000001c9c380 > (XEN) ffff830000f80438 ffff830000f80438 ffff83007a2c4178 0000000000000037 > (XEN) ffff83007cc28000 ffff83007cc28000 ffff83007d796000 0000000000000000 > (XEN) 0000000000004016 ffff828c80243100 ffff828c8019b9aa ffff828c801188a8 > (XEN) ffff83007d78ff28 ffff83007d78ff28 ffff828c80286900 ffff83007cc28000 > (XEN) ffff83007cc28000 ffff83007d796000 0000001c8063eb1f 0000000000000000 > (XEN) ffff828c8019b778 0000000000000000 ffffffff80590f00 ffffffffffffffff > (XEN) 0000000000000000 0000000000093380 00000003a2498219 0000000000000000 > (XEN) 0000000000000001 00000000ffffffff 0000000000093380 00000003a2498219 > (XEN) 00000003a2498219 000000000000000f 000000002437ac19 ffffffff80561f48 > (XEN) 000000f000000000 ffffffff8020adb0 0000000000000000 0000000000000296 > (XEN) ffffffff80561f68 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 000000000000000f ffff83007cc28000 > (XEN) Xen call trace: > (XEN) [<ffff828c8013c391>] __find_next_bit+0x21/0x70 > (XEN) [<ffff828c8012f8e5>] hvm_dirq_assist+0xa5/0x2d0 > (XEN) [<ffff828c8019b9aa>] vmx_intr_assist+0x5a/0x220 > (XEN) [<ffff828c801188a8>] do_softirq+0x58/0x80 > (XEN) [<ffff828c8019b778>] vmx_asm_do_vmentry+0x5/0xdd > (XEN) > (XEN) > (XEN) **************************************** > (XEN) Panic on CPU 15: > (XEN) GENERAL PROTECTION FAULT > (XEN) [error_code=0000] > (XEN) **************************************** > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel