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/
Home Products Support Community News


[Xen-bugs] [Bug 1417] New: [VT-d] Xen hypervisor will crash at booting i

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1417] New: [VT-d] Xen hypervisor will crash at booting if vt-d is enabled
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 14 Feb 2009 04:58:25 -0800
Delivery-date: Sat, 14 Feb 2009 04:58:32 -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

           Summary: [VT-d] Xen hypervisor will crash at booting if vt-d is
           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

Service Arch (ia32/ia32e/IA64): ia32pae ia32e
Guest Arch (ia32/ia32e/IA64): 
Guest OS Type (Linux/Windows):
Change Set: 19196
Hardware: NHM-HEDT, Stoakley

Bug detailed description:
Xen hypervisor with VT-d enabled will crash at booting with following log:

(XEN) Intel machine check reporting enabled on CPU#7.                          
(XEN) CPU7: Thermal monitoring enabled (TM2)                                   
(XEN) CMCI: CPU7 has no CMCI support                                           
(XEN) CPU7: Intel(R) Xeon(R) CPU           X5376  @ 2.80GHz stepping 0b        
(XEN) Total of 8 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 8 CPUs: passed.                      
(XEN) Platform timer is 3.579MHz ACPI PM Timer                                 
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed                            
(XEN) microcode.c:73:d32767 microcode: CPU7 resumed                            
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed                            
(XEN) microcode.c:73:d32767 microcode: CPU5 resumed                            
(XEN) Brought up 8 CPUs                                                        
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed                            
(XEN) ----[ Xen-3.4-unstable  x86_64  debug=y  Not tainted ]----               
(XEN) microcode.c:73:d32767 microcode: CPU6 resumed                            
(XEN) CPU:    0                                                                
(XEN) microcode.c:73:d32767 microcode: CPU4 resumed                            
(XEN) RIP:    e008:[<ffff828c8011b591>] check_lock+0x19/0x4e                   
(XEN) RFLAGS: 0000000000010046   CONTEXT: hypervisor                           
(XEN) rax: 0000000000000001   rbx: 0000000000000040   rcx: 0000000000000001    
(XEN) rdx: 0000000000000082   rsi: 0000000000000001   rdi: 0000000000000044    
(XEN) rbp: ffff828c80277c58   rsp: ffff828c80277c58   r8:  0000000000000004    
(XEN) r9:  0000000000000001   r10: 0000000000000001   r11: 0000000000000000    
(XEN) r12: 0000000000000082   r13: 0000000000000282   r14: 0000000000000090    
(XEN) r15: ffff83022ff937e0   cr0: 000000008005003b   cr4: 00000000000026f0    
(XEN) cr3: 00000000cfc7c000   cr2: 0000000000000044                            
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008          
(XEN) Xen stack trace from rsp=ffff828c80277c58:                               
(XEN)    ffff828c80277c78 ffff828c8011b70c 0000000000000000 0000000000000040   
(XEN)    ffff828c80277c98 ffff828c8012df24 ffff828c802a1c00 ffff828c802a1c24   
(XEN)    ffff828c80277ca8 ffff828c8012df83 ffff828c80277ce8 ffff828c80147cc0   
(XEN)    ffff828c80277ce8 00000000fffffff4 0000000000000090 ffff828c8012e3a7   
(XEN)    ffff828c801e2279 ffff83022ff933a0 ffff828c80277d28 ffff828c801481fa   
(XEN)    ffff83022ff937e0 0000000000000090 ffff83022ff933a0 0000000000004800   
(XEN)    ffff83022ff933a0 ffff828c8029d400 ffff828c80277d68 ffff828c8012e32f   
(XEN)    ffff828c80277d48 0000000000000004 ffff83022ff933a0 0000000000000282   
(XEN)    ffff83022fff16b0 0000000000100000 ffff828c80277d98 ffff828c8012eff7   
(XEN)    0000000000000004 ffff83022ff936e0 ffff828c8020bab0 0000000000000020   
(XEN)    ffff828c80277de8 ffff828c8012f586 ffff828c80277dd8 ffff828c8012a183   
(XEN)    0000000000000004 00010001802095c0 0001000100010001 00000000ffffffed   
(XEN)    ffff828c8022ec08 0000000000000007 ffff828c80277e08 ffff828c8012be18   
(XEN)    ffff828c80277e08 ffff828c8022eaf8 ffff828c80277f18 ffff828c80222ca8   
(XEN)    0000000000000000 0000000000000000 0000000000000000 ffff828c8020e675   
(XEN)    ffffffffc0270000 ffff8300cfc7cff8 ffff8300cfc7dff8 000000000020e610   
(XEN)    000000000008bf30 0000000000000000 0000000000000000 0000000000000000   
(XEN)    ffff83000008bfc0 ffff83000008bf30 0000000000afd000 0000000000000000   
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000   
(XEN)    0000000000000000 0000000000000000 0000000800000000 000000010000006e   
(XEN) Xen call trace:                                                          
(XEN)    [<ffff828c8011b591>] check_lock+0x19/0x4e                             
(XEN)    [<ffff828c8011b70c>] _spin_lock_irqsave+0x21/0x3f                     
(XEN)    [<ffff828c8012df24>] dma_msi_unmask+0x2a/0x4b                         
(XEN)    [<ffff828c8012df83>] dma_msi_startup+0x9/0x10                         
(XEN)    [<ffff828c80147cc0>] setup_irq_vector+0x73/0x99                       
(XEN)    [<ffff828c801481fa>] request_irq_vector+0x6c/0x9a                     
(XEN)    [<ffff828c8012e32f>] iommu_set_interrupt+0x97/0x10f                   
(XEN)    [<ffff828c8012eff7>] init_vtd_hw+0x13a/0x2d1                          
(XEN)    [<ffff828c8012f586>] intel_vtd_setup+0x32e/0x42e                      
(XEN)    [<ffff828c8012be18>] iommu_setup+0x2d/0xf5                            
(XEN)    [<ffff828c80222ca8>] __start_xen+0x457d/0x4895                        
(XEN) Pagetable walk from 0000000000000044:                                    
(XEN)  L4[0x000] = 000000022fff0063 5555555555555555                           
(XEN)  L3[0x000] = 000000022ffef063 5555555555555555                           
(XEN)  L2[0x000] = 000000022ffee063 5555555555555555                           
(XEN)  L1[0x000] = 0000000000000000 ffffffffffffffff                           
(XEN) ****************************************                                 
(XEN) Panic on CPU 0:                                                          
(XEN) FATAL PAGE FAULT                                                         
(XEN) [error_code=0000]                                                        
(XEN) Faulting linear address: 0000000000000044                                
(XEN) ****************************************                                 
(XEN) Reboot in five seconds...

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

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