[Xen-bugs] [Bug 1627] New: Kernel panic with 2.6.33.5 in a domU

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1627

           Summary: Kernel panic with 2.6.33.5 in a domU
           Product: Xen
           Version: unspecified
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Linux-pv_ops domU
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: major.hayden@xxxxxxxxxxxxx


We've received a report about a kernel panic when running 2.6.33.5 (from
kernel.org) within a domU.  The Xen hypervisor is version 3.3.0.

[366377.232546] Pid: 17344, comm: 6.out Tainted: G      D    2.6.33.5-rscloud
#2                                        
[366377.232546] Call Trace:                                                     
[366377.232546]  [<ffffffff812213fa>] ? panic+0x78/0x12f                        
[366377.232546]  [<ffffffff8100afb8>] ? oops_end+0x86/0x93                      
[366377.232546]  [<ffffffff81008ee0>] ? do_alignment_check+0x88/0x92            
[366377.232546]  [<ffffffff810082f5>] ? alignment_check+0x25/0x30               
[366377.232546]  [<ffffffffa006c41e>] ? inet6_csk_xmit+0x42/0x28f [ipv6]        
[366377.232546]  [<ffffffff81004e25>] ? xen_force_evtchn_callback+0x9/0xa       
[366377.232546]  [<ffffffff810054b2>] ? check_events+0x12/0x20                  
[366377.232546]  [<ffffffff81004e25>] ? xen_force_evtchn_callback+0x9/0xa       
[366377.232546]  [<ffffffff810054b2>] ? check_events+0x12/0x20                  
[366377.232546]  [<ffffffffa006700e>] ? tcp_v6_send_check+0x8e/0x9b [ipv6]      
[366377.232546]  [<ffffffff811e8274>] ? tcp_transmit_skb+0x6c1/0x6ff            
[366377.232546]  [<ffffffff8100549f>] ? xen_restore_fl_direct_end+0x0/0x1       
[366377.232546]  [<ffffffff8108ccf3>] ? __kmalloc+0x97/0xba                     
[366377.232546]  [<ffffffff8100549f>] ? xen_restore_fl_direct_end+0x0/0x1       
[366377.232546]  [<ffffffff811e8464>] ? tcp_send_active_reset+0xef/0x156        
[366377.232546]  [<ffffffff811dd8c4>] ? tcp_disconnect+0x7f/0x339               
[366377.232546]  [<ffffffff811dc286>] ? inet_csk_listen_stop+0x7b/0x13e         
[366377.232546]  [<ffffffff811ddbb5>] ? tcp_close+0x37/0x37e                    
[366377.232546]  [<ffffffff811f9a6a>] ? inet_release+0x4e/0x54                  
[366377.232546]  [<ffffffff811a3761>] ? sock_release+0x19/0x68                  
[366377.232546]  [<ffffffff811a37d2>] ? sock_close+0x22/0x27                    
[366377.232546]  [<ffffffff81091b25>] ? __fput+0xef/0x194                       
[366377.232546]  [<ffffffff8108f063>] ? filp_close+0x5f/0x6a                    
[366377.232546]  [<ffffffff8102ec8d>] ? put_files_struct+0x67/0xbf              
[366377.232546]  [<ffffffff8122316e>] ? _raw_spin_lock_irq+0x7/0x1c             
[366377.232546]  [<ffffffff810303f0>] ? do_exit+0x209/0x670                     
[366377.232546]  [<ffffffff810308c9>] ? do_group_exit+0x72/0x9a                 
[366377.232546]  [<ffffffff81038959>] ? get_signal_to_deliver+0x302/0x323       
[366377.232546]  [<ffffffff81006ac1>] ? do_signal+0x6a/0x675                    
[366377.232546]  [<ffffffff8100549f>] ? xen_restore_fl_direct_end+0x0/0x1       
[366377.232546]  [<ffffffff8100335d>] ? xen_mc_flush+0x158/0x183                
[366377.232546]  [<ffffffff8100549f>] ? xen_restore_fl_direct_end+0x0/0x1       
[366377.232546]  [<ffffffff810027d7>] ? xen_end_context_switch+0xe/0x1c         
[366377.232546]  [<ffffffff810025b8>] ? xen_write_msr_safe+0x5d/0x75            
[366377.232546]  [<ffffffff810061e0>] ? __switch_to+0x12f/0x21b                 
[366377.232546]  [<ffffffff810070d9>] ? do_notify_resume+0xd/0x41               
[366377.232546]  [<ffffffff8100780e>] ? int_signal+0x12/0x17  

The panic always occurs when compiling the Go language source tree.  I can
reproduce it myself with 2.6.33.5 and 2.6.32.12 - both from kernel.org.


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