[Xen-devel] Linux kernel 3.12 regression, Dom0 fails to boot on Core 2 6400

[Wei Liu <wei.liu2@xxxxxxxxxx>]

Hi Konrad

Just notice a regression on 3.12 kernel, Dom0 fails to boot early on
with following message:

(XEN) traps.c:455:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 
[ec=0000]
(XEN) domain_crash_sync called from entry.S                                     
   
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:                                       
(XEN) ----[ Xen-4.4-unstable  x86_64  debug=y  Tainted:    C ]----              
(XEN) CPU:    0                                                                 
(XEN) RIP:    e033:[<ffffffff81b6a48e>]                                         
(XEN) RFLAGS: 0000000000000292   EM: 1   CONTEXT: pv guest                      
(XEN) rax: 000000000000006a   rbx: ffffffff8148c255   rcx: 00000000000000aa     
   
(XEN) rdx: 0000000000000032   rsi: 0000000000000006   rdi: 0000000000000000     
   
(XEN) rbp: ffffffff82201e38   rsp: ffffffff82201dd8   r8:  0000000000000000     
   
(XEN) r9:  6465746365707865   r10: 000000000000009d   r11: 6820746120706f20     
   
(XEN) r12: ffffffff810199e0   r13: ffffffff82309c18   r14: ffffffff81c01f04     
   
(XEN) r15: 0000000000000000   cr0: 0000000080050033   cr4: 00000000000026f0     
   
(XEN) cr3: 000000021e20c000   cr2: 0000000000000000                             
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033           
(XEN) Guest stack trace from rsp=ffffffff82201dd8:                              
(XEN)    00000000000000aa 6820746120706f20 ffffffff81b6a48e 000000010000e030    
   
(XEN)    0000000000010092 ffffffff82201e18 000000000000e02b ffffffff81b6a48e    
   
(XEN)    ffffffff00000000 ffffffff00000000 ffffffff81ffb05d ffffffff00000035    
   
(XEN)    ffffffff82201e78 ffffffff810176a4 ffffffe800000000 90666666663a3e50    
   
(XEN)    ffffffff82309c10 0000000000000001 ffffffff824b3c20 ffff88021a138740    
   
(XEN)    ffffffff82201ea8 ffffffff81017889 ffffffff82305a58 0000441f0f000000    
   
(XEN)    ffffffff824b3c40 ffffffff82309c10 ffffffff82201ed8 ffffffff823549f5    
   
(XEN)    0000000000000065 ffffffffffffffff ffffffff823d0020 ffffffff823da2e0    
   
(XEN)    ffffffff82201f28 ffffffff82331ca5 ffffffff8233186d ffffffff82652000    
   
(XEN)    ffffffff82659038 ffffffff823da2e0 00000000f3dfffff 0000000000000000    
(XEN)    0000000000000000 0000000000000000 ffffffff82201f38 ffffffff823315e0    
(XEN)    ffffffff82201ff8 ffffffff82335484 0000000100000000 00020800000006f6    
(XEN)    1fc9cbf580002281 0300000100000032 0000000000000005 0000000000000020    
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000    
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000    
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000    
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000    
(XEN)    0000000000000000 0f00000060c0c748 ccccccccccccc305 cccccccccccccccc    
(XEN)    cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc    
(XEN)    cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc    
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.

Biscetion shows that it's due to the change in jump label.

commit 442e0973e9273ae8832abd70f52efde8b8326178                                 
Merge: 8d7551e fb40d7a                                                          
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>                          
Date:   Tue Sep 10 19:43:23 2013 -0700                                          
                                                                                
    Merge branch 'x86/jumplabel' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
                                                                                
    Pull x86 jumplabel changes from Peter Anvin:                                
     "One more x86 tree for this merge window.  This tree improves the          
      handling of jump labels, so that most of the time we don't have to do     
      a massive initial patching run.                                           
                                                                                
      Furthermore, we will error out of the jump label is not what is           
      expected, eg if it has been corrupted or tampered with"                   
                                                                                
    * 'x86/jumplabel' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: 
      x86/jump-label: Show where and what was wrong on errors                   
      x86/jump-label: Add safety checks to jump label conversions               
      x86/jump-label: Do not bother updating nops if they are correct           
      x86/jump-label: Use best default nops for inital jump label calls 

Hardware matters. I can only see the crash on Intel(R) Core(TM)2 6400 @
2.13GHz.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel