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 1312] New: [Xen-3.2.2-RC1]Domain0 will crash when wake u

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1312] New: [Xen-3.2.2-RC1]Domain0 will crash when wake up from S3 on IA32E
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 31 Jul 2008 07:12:01 -0700
Delivery-date: Thu, 31 Jul 2008 07:12:05 -0700
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: [Xen-3.2.2-RC1]Domain0 will crash when wake up from S3
                    on IA32E
           Product: Xen
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx

Service OS (ia32/ia32e/IA64): ia32e
Guest OS (ia32/ia32e/IA64): 
Change Set: xen 3.2.2-rc1 #16957
Hardware: Stoakley/Clovertown

Bug detailed description:
On IA32E with SMP cpus, Dom0 S3 can sleep, but when it wake, Dom0 will crash.
IA32PAE can do Dom0 S3 successfully.

Reproduce steps:

Current result:

Expected result:

Basic root-causing log:
Restarting tasks...<6>usb 2-1: USB disconnect, address 3                        
Thawing cpus ...                                                                
Initializing CPU#1                                                              
CPU1 is up                                                                      
Initializing CPU#2                                                              
CPU2 is up                                                                      
Initializing CPU#3                                                              
CPU3 is up                                                                      
Initializing CPU#4                                                              
CPU4 is up                                                                      
Initializing CPU#5                                                              
general protection fault: 0000 [1] SMP                                          
CPU 5                                                                           
Modules linked in: bridge ipv6 hidp l2cap bluetooth nfs lockd nfs_acl sunrpc
Pid: 0, comm: swapper Tainted: GF #1                           
RIP: e030:[<ffffffff80213b5f>]  [<ffffffff80213b5f>]
RSP: e02b:ffff880025c47eb8  EFLAGS: 00010006                                    
RAX: ffff88000632dfd8 RBX: 00007fff00000001 RCX: 0000000000000000               
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 00007fff00000001               
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000               
R10: 0000000000000000 R11: 0000000000000246 R12: 547d42ae00000004               
R13: 0000000000000000 R14: ffff88000632de88 R15: ffff88000632de88               
FS:  0000000000000000(0000) GS:ffffffff804d9280(0000) knlGS:0000000000000000    
CS:  e033 DS: 002b ES: 002b                                                     
Process swapper (pid: 0, threadinfo ffff88000632c000, task ffff8800063090c0)    
Stack:  ffff88003d3c6240 0000000000000000 0000000000000110 ffffffff80258b9c     
 ffffffff804e2c80 0000000000008800 0000000000000110 ffff88003d3c6240            
 ffffffff804e2cbc ffffffff80258c88 0000000000000000 0000000000000110            
Call Trace:                                                                     
 <IRQ> [<ffffffff80258b9c>] handle_IRQ_event+0x4e/0x96                          
 [<ffffffff80258c88>] __do_IRQ+0xa4/0x105                                       
 [<ffffffff8020d035>] do_IRQ+0x65/0x73                                          
 [<ffffffff8034bad2>] evtchn_do_upcall+0x13b/0x1fb                              
 [<ffffffff8020ad8e>] do_hypervisor_callback+0x1e/0x2c                          
 <EOI> [<ffffffff80201000>] init_level4_pgt+0x0/0x1000                          
 [<ffffffff8020622a>] hypercall_page+0x22a/0x1000                               
 [<ffffffff8020622a>] hypercall_page+0x22a/0x1000                               
 [<ffffffff8034aab2>] force_evtchn_callback+0xa/0xb                             
 [<ffffffff8020901a>] cpu_idle+0xa1/0xce                                        

Code: 41 ff d4 e8 ee 0e 02 00 45 85 ed 74 11 0f ae f0 48 8b 05 1a               
RIP  [<ffffffff80213b5f>] smp_call_function_interrupt+0x4c/0x75                 
 RSP <ffff880025c47eb8>                                                         
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!                
 (XEN) Domain 0 crashed: rebooting machine in 5 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>