WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Stephen Smalley <sds@xxxxxxxxxxxxx>, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
Subject: Re: [Xen-devel] Xen BUG at msi.c:391
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 20 Aug 2009 17:02:59 +0100
Cc: Xen <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 20 Aug 2009 09:03:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1250781518.2390.9.camel@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcohqQO3FMN6n7ycSEmS4ycjUyVO2gABqxXR
Thread-topic: [Xen-devel] Xen BUG at msi.c:391
User-agent: Microsoft-Entourage/12.20.0.090605
Looks like a lock normally taken with irqs disabled may be being taken with
irqs enabled. Which wouldn't be allowed but could be easy to fix.

 -- Keir

On 20/08/2009 16:18, "Stephen Smalley" <sds@xxxxxxxxxxxxx> wrote:

> Hi,
> 
> Your two patches fixed the problem on x86_32, but we now see the
> following BUG on booting changeset 20093:e83bb28d48fe on a Dell Optiplex
> 960 Core 2 Quad.
> 
> (XEN) Initializing CPU#0
> (XEN) Detected 2992.543 MHz processor.
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 6144K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU: Processor Core ID: 0
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN) HVM: VMX enabled
> (XEN) Intel machine check reporting enabled on CPU#0.
> (XEN) CPU0: Thermal monitoring enabled (TM2)
> (XEN) CMCI: CPU0 has no CMCI support
> (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU    Q9650  @ 3.00GHz stepping 0a
> (XEN) Booting processor 1/1 eip 8c000
> (XEN) Initializing CPU#1
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 6144K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU: Processor Core ID: 1
> (XEN) Intel machine check reporting enabled on CPU#1.
> (XEN) CPU1: Thermal monitoring enabled (TM2)
> (XEN) CMCI: CPU1 has no CMCI support
> (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU    Q9650  @ 3.00GHz stepping 0a
> (XEN) Booting processor 2/2 eip 8c000
> (XEN) Initializing CPU#2
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 6144K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU: Processor Core ID: 2
> (XEN) Intel machine check reporting enabled on CPU#2.
> (XEN) CPU2: Thermal monitoring enabled (TM2)
> (XEN) CMCI: CPU2 has no CMCI support
> (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU    Q9650  @ 3.00GHz stepping 0a
> (XEN) Booting processor 3/3 eip 8c000
> (XEN) Initializing CPU#3
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 6144K
> (XEN) CPU: Physical Processor ID: 0
> (XEN) CPU: Processor Core ID: 3
> (XEN) Intel machine check reporting enabled on CPU#3.
> (XEN) CPU3: Thermal monitoring enabled (TM2)
> (XEN) CMCI: CPU3 has no CMCI support
> (XEN) CPU3: Intel(R) Core(TM)2 Quad CPU    Q9650  @ 3.00GHz stepping 0a
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
> (XEN) checking TSC synchronization across 4 CPUs: passed.
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) microcode.c:73:d32767 microcode: CPU1 resumed
> (XEN) Brought up 4 CPUs
> (XEN) microcode.c:73:d32767 microcode: CPU2 resumed
> (XEN) microcode.c:73:d32767 microcode: CPU3 resumed
> (XEN) I/O virtualisation disabled
> (XEN) Xen BUG at spinlock.c:24
> (XEN) ----[ Xen-3.5-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    0  
> (XEN) RIP:    e008:[<ffff828c8011ba81>] check_lock+0x39/0x45
> (XEN) RFLAGS: 0000000000010246   CONTEXT: hypervisor
> (XEN) rax: 0000000000000001   rbx: ffff828c802302fc   rcx: 0000000000000000
> (XEN) rdx: 0000000000000001   rsi: 0000000000000001   rdi: ffff828c80230300
> (XEN) rbp: ffff828c8029fd40   rsp: ffff828c8029fd40   r8:  ffff830237ef0004
> (XEN) r9:  000000000000000c   r10: 0000000000000000   r11: 0000000000000040
> (XEN) r12: ffff830237e80c80   r13: ffff830237ed0310   r14: 0000000000000018
> (XEN) r15: 0000000000000008   cr0: 000000008005003b   cr4: 00000000000026f0
> (XEN) cr3: 00000000bfaa4000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff828c8029fd40:
> (XEN)    ffff828c8029fd58 ffff828c8011be43 0000000000000001 ffff828c8029fd68
> (XEN)    ffff828c8015fe26 ffff828c8029fd98 ffff828c8015b6ec 0000000000000018
> (XEN)    0000000000000018 ffff830237ed0310 0000000000000000 ffff828c8029fdd8
> (XEN)    ffff828c8018f57b 0000000000000000 0000000000000000 ffff828c8029fdd8
> (XEN)    0000000000000000 0000000000000100 ffff828c802d2080 ffff828c8029fe58
> (XEN)    ffff828c8018f8a4 ffff828c8029fe18 0000000000000060 0000001880255a48
> (XEN)    0000000000da7a63 ffff828c80258a88 0000001800000000 00000000fee0f00c
> (XEN)    ffff828c00004198 00000000ffffffed ffff828c80257dd8 ffff828c80257ea8
> (XEN)    ffff83000008bfc0 ffff83000008bf60 ffff828c80236ea0 ffff828c8029fe68
> (XEN)    ffff828c80175307 ffff828c8029ff18 ffff828c8024aea4 0000000000000000
> (XEN)    0000000000000000 0000000000000000 00000000011d0fe4 ffff83000008bf60
> (XEN)    0000000000000000 00000000ffffffff ffff830000000003 0000000800000000
> (XEN)    000000010000006e 0000000000000003 00000000000002f8 0000000000000000
> (XEN)    0000000100000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000067ddc
> (XEN)    ffff828c801000b5 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)    [<ffff828c8011ba81>] check_lock+0x39/0x45
> (XEN)    [<ffff828c8011be43>] _spin_lock+0x11/0x3f
> (XEN)    [<ffff828c8015fe26>] lock_vector_lock+0x10/0x12
> (XEN)    [<ffff828c8015b6ec>] set_desc_affinity+0x37/0x84
> (XEN)    [<ffff828c8018f57b>] hpet_msi_set_affinity+0x30/0xd4
> (XEN)    [<ffff828c8018f8a4>] hpet_broadcast_init+0x237/0x537
> (XEN)    [<ffff828c80175307>] disable_pit_irq+0x34/0x8a
> (XEN)    [<ffff828c8024aea4>] __start_xen+0x233a/0x2616
> (XEN)            
> (XEN)            
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Xen BUG at spinlock.c:24
> (XEN) ****************************************
> (XEN)            
> (XEN) Reboot in five seconds...                                               
>   



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

<Prev in Thread] Current Thread [Next in Thread>