RE: [Xen-devel] Xen BUG at msi.c:391

["Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>]

Could you apply the following patch to see whether it works or not ? 
Xiantao

diff -r a3ae60f8b546 xen/arch/x86/io_apic.c
--- a/xen/arch/x86/io_apic.c    Wed Aug 19 17:00:26 2009 +0100
+++ b/xen/arch/x86/io_apic.c    Thu Aug 20 12:36:33 2009 +0800
@@ -2393,7 +2393,7 @@ void __init init_ioapic_mappings(void)
         }
     }

-    nr_irqs_gsi = max(nr_irqs, highest_gsi());
+    nr_irqs_gsi = highest_gsi();

     if ( !smp_found_config || skip_ioapic_setup || nr_irqs_gsi < 16 )
         nr_irqs_gsi = 16;

Stephen Smalley wrote:
> I get the following BUG every time when trying to start xend after
> booting the current xen-unstable tip (20088:4e2ffbd99aeb). 
> Yesterday's 
> tip was fine for me.  Only happens on x86_32.
> 
> (XEN) Xen BUG at msi.c:391
> (XEN) ----[ Xen-3.5-unstable  x86_32p  debug=y  Not tainted ]----
> (XEN) CPU:    1
> (XEN) EIP:    e008:[<ff152aff>] msi_set_mask_bit+0x45/0x104
> (XEN) EFLAGS: 00210046   CONTEXT: hypervisor
> (XEN) eax: 00000001   ebx: 00000000   ecx: ffb201a0   edx: 00000001
> (XEN) esi: 00000001   edi: 00000402   ebp: ffbcbdbc   esp: ffbcbd74
> (XEN) cr0: 8005003b   cr4: 000026f0   cr3: 002d0ca0   cr2: b7ff1ea0
> (XEN) ds: e010   es: e010   fs: 00d8   gs: 0033   ss: e010   cs: e008
> (XEN) Xen stack trace from esp=ffbcbd74:
> (XEN)    ffb2019c 00200282 00000020 00000000 80090000 00200082
> ffbcbd9c ff1186ac (XEN)    00000002 00200282 ffbcbdcc ff16309d
> ff204694 00200282 ffbcbdcc 00000402 (XEN)    ffb2019c 00000402
> ffbcbdcc ff152d72 00000058 ffb20180 ffbcbdec ff14f583 (XEN)   
> 00000402 00200086 ffbcbdec ff1186ac ffb20180 ffb2019c ffbcbe2c
> ff15445c (XEN)    00000402 00000000 00000000 0000005a 00000086
> 00200282 00000000 00200286 (XEN)    80090000 00000058 0000005a
> 00000402 000007fd ff2f2000 ffbcbe4c ff15669f (XEN)    00000402
> 00000009 ffbcbe8c ff1529db 00000009 ff2ce510 ffbcbe8c ff1535b7 (XEN) 
> 00000402 00020100 ffbcbe8c ff152665 ffb2019c 00000001 00001ff4
> 00000000 (XEN)    00000018 00200086 ffbcbe8c 000007fd 000007fd
> ff2f2000 ffbcbeec ff155a2a (XEN)    ff2ce510 00200286 00000000
> ff116642 ff2d0024 d397995d 0000001c ffbf5988 (XEN)    00200286
> 00000402 ffb2019c 0000001c 00001ff4 00000402 ffb20180 ff2ce510 (XEN) 
> ffbcbf34 df365b20 00200202 fffffffd ff2f2000 ff2f2074 ffbcbf8c
> ff1639cd (XEN)    ff2f2000 000007fd 00000008 ff10701e ffbcbf64
> df365b20 00000004 00000000 (XEN)    ff2d0024 ffffffff 7fffffff
> 0000001c d3985cad 0000001c ffbcbf7c ff11a338 (XEN)    df367ff0
> 000007fd c0454f02 c0454efc ff2d0000 ff224100 d397995d 0000001c (XEN) 
> ffbf5ad0 ffbf5ad0 ff2d0034 ff224100 00000018 aaaaaaaa aaaaaaaa
> ff274b80 (XEN)    0000007b ffbcbfb4 ffbcbfac ff2d0000 00000021
> ffbcbfac 00434037 ff1cc038 (XEN)    0000000e df365b20 deadbeef
> deadbeef deadbeef deadbeef c0201427 00000021 (XEN)    0000000e
> df365b20 00000000 df7734a0 00001003 df365b34 00000021 00f90000 (XEN) 
> c0201427 00000061 00200202 df365b00 00000069 0000007b 0000007b
> 000000d8 (XEN) Xen call trace: (XEN)    [<ff152aff>]
> msi_set_mask_bit+0x45/0x104 (XEN)    [<ff152d72>]
> mask_msi_irq+0x16/0x23 (XEN)    [<ff14f583>]
> shutdown_msi_irq+0x11/0x13 (XEN)    [<ff15445c>]
> dynamic_irq_cleanup+0x31/0x8b (XEN)    [<ff15669f>]
> destroy_irq+0x2c/0x3d (XEN)    [<ff1535b7>] msi_free_irq+0x158/0x172
> (XEN)    [<ff155a2a>] unmap_domain_pirq+0x28c/0x30b (XEN)   
> [<ff1639cd>] do_physdev_op+0x84e/0xf31 (XEN)    [<ff1cc038>]
> hypercall+0xb8/0xd8 (XEN) (XEN) (XEN)
> **************************************** (XEN) Panic on CPU 1: (XEN)
> Xen BUG at msi.c:391 (XEN) ****************************************


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