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-bugs

[Xen-bugs] [Bug 1416] New: cpu offline causes Xen panic.

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1416] New: cpu offline causes Xen panic.
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 14 Feb 2009 04:40:30 -0800
Delivery-date: Sat, 14 Feb 2009 04:40:42 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1416

           Summary: cpu offline causes Xen panic.
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx


Environment:
------------
Service Arch (ia32/ia32e/IA64): all 
Guest Arch (ia32/ia32e/IA64): all
Guest OS Type (Linux/Windows): 
Change Set: c/s 19186
Hardware: 
Other:


Bug detailed description:
--------------------------
When doing cpu offline, Xen panics with following log:


(XEN) Prepare to bring CPU1 down...                                            
(XEN) deleting CPU 1                                                           
(XEN) Assertion '_spin_is_locked(&irq_desc[vector].lock)' failed at msi.c:233  
(XEN) ----[ Xen-3.4-unstable  x86_64  debug=y  Not tainted ]----               
(XEN) CPU:    1                                                                
(XEN) RIP:    e008:[<ffff828c80147890>] set_msi_affinity+0x90/0x1d0            
(XEN) RFLAGS: 0000000000010046   CONTEXT: hypervisor                           
(XEN) rax: 0000000000000000   rbx: ffff83022ff66360   rcx: 0000000000000001    
(XEN) rdx: 0000000000000002   rsi: 0000000000000040   rdi: ffff828c8029e4a8    
(XEN) rbp: ffff83022ffdfdf0   rsp: ffff83022ffdfda0   r8:  0000000000000020    
(XEN) r9:  ffff828c8020d600   r10: ffff83022fff18b8   r11: 0000000000000246    
(XEN) r12: 0000000000000021   r13: 0000000000000021   r14: ffff828c8029e498    
(XEN) r15: ffff828c8020ce44   cr0: 000000008005003b   cr4: 00000000000026b0    
(XEN) cr3: 00000000cfc7c000   cr2: 000000352ec948a0                            
(XEN) ds: 002b   es: 002b   fs: 0000   gs: 0000   ss: e010   cs: e008          
(XEN) Xen stack trace from rsp=ffff83022ffdfda0:                               
(XEN)    ffff828c801f8e0c 0000004000000086 0000000000000000 ffff828c00000000   
(XEN)    0000000000000086 ffff828c8020ce44 0000000000000021 0000000000000021   
(XEN)    ffff828c8029e498 ffff828c8020ce44 ffff83022ffdfe00 ffff828c801437c0   
(XEN)    ffff83022ffdfe40 ffff828c801487be 00000000000000fd 0000000000000020   
(XEN)    0000000000000007 0000000000000001 ffff828c8020d608 ffff828c8020d708   
(XEN)    ffff83022ffdfea0 ffff828c8015b0d2 0000000000000002 0000000000000008   
(XEN)    00000000000000fd ffff828c801761a6 000000000000e008 0000000000000003   
(XEN)    ffff83022ffdff28 ffff828c8028f900 0000000000000002 ffff828c80231100   
(XEN)    ffff83022ffdfeb0 ffff828c8015b0ff ffff83022ffdfed0 ffff828c8011ba36   
(XEN)    0000000000000001 ffff83022ffdff28 ffff83022ffdff00 ffff828c8011b291   
(XEN)    ffff828c8022f5b0 ffff83022ffdff28 ffff828c8022f5b0 ffff8300cfef2000   
(XEN)    ffff83022ffdff20 ffff828c8013ba26 0000000000000001 ffff8300cfafc000   
(XEN)    ffff83022ffdfdb8 0000000000000000 0000000000000000 0000000000000000   
(XEN)    0000000000000000 0000000000000000 0000000000000007 0000000000000246   
(XEN)    0000000000000000 ffff880070d93988 ffff880007650000 0000000000000000   
(XEN)    ffffffff802063aa 0000000000000000 00000000deadbeef 00000000deadbeef   
(XEN)    0000010000000000 ffffffff802063aa 000000000000e033 0000000000000246   
(XEN)    ffff880007651f08 000000000000e02b 000000000000beef 000000000000beef   
(XEN)    000000000000beef 000000000000beef 0000000000000001 ffff8300cfafc000   
(XEN) Xen call trace:                                                          
(XEN)    [<ffff828c80147890>] set_msi_affinity+0x90/0x1d0                      
(XEN)    [<ffff828c801437c0>] set_msi_affinity_vector+0x1b/0x1d                
(XEN)    [<ffff828c801487be>] fixup_irqs+0xc7/0x1bf                            
(XEN)    [<ffff828c8015b0d2>] __cpu_disable+0x1bf/0x1e3                        
(XEN)    [<ffff828c8015b0ff>] take_cpu_down+0x9/0xe                            
(XEN)    [<ffff828c8011ba36>] stopmachine_softirq+0x5f/0x7a                    
(XEN)    [<ffff828c8011b291>] do_softirq+0x6a/0x77                             
(XEN)    [<ffff828c8013ba26>] idle_loop+0x9a/0x9c                              
(XEN)                                                                          
(XEN)                                                                          
(XEN) ****************************************                                 
(XEN) Panic on CPU 1:                                                          
(XEN) Assertion '_spin_is_locked(&irq_desc[vector].lock)' failed at msi.c:233  
(XEN) ****************************************                                 
(XEN)                                                                          
(XEN) Reboot in five seconds...


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

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