2016-03-18 32 views
-1
Message from [email protected] at Mar 18 13:24:54 ... 
kernel:BUG: soft lockup - CPU#30 stuck for 61s! [events/30:161] 

Message from [email protected] at Mar 18 13:24:54 ... 
kernel:Process events/30 (pid: 161, ti=f4ea4000 task=f4e5faa0 task.ti=f4ea4000) 

Message from [email protected] at Mar 18 13:24:54 ... 
kernel:Stack: 

Message from [email protected] at Mar 18 13:24:54 ... 
kernel:Call Trace: 

Message from [email protected] at Mar 18 13:24:54 ... 
kernel:Code: 00 89 51 04 89 0a 89 43 20 89 43 24 8b 43 08 39 d8 74 23 83 40 7c 01 31 c9 8b 7b 0c 8b 15 58 09 ac c0 8b 02 39 c2 75 09 eb 31 90 <8b> 00 39 d0 74 2a 3b 78 0c 75 f5 89 d8 ba 00 00 04 00 e8 b9 a0 

Message from [email protected] at Mar 18 13:24:58 ... 
kernel:BUG: soft lockup - CPU#8 stuck for 61s! [buildop:2223] 

Message from [email protected] at Mar 18 13:24:58 ... 
kernel:Process buildop (pid: 2223, ti=e9724000 task=f3ba0aa0 task.ti=e9724000) 

Message from [email protected] at Mar 18 13:24:58 ... 
kernel:Stack: 

Message from [email protected] at Mar 18 13:24:58 ... 
kernel:Call Trace: 

Message from [email protected] at Mar 18 13:24:58 ... 
kernel:Code: 26 00 89 c8 f0 81 28 00 00 00 01 74 05 e8 2c fe ff ff c3 8d b4 26 00 00 00 00 66 ba 00 01 f0 66 0f c1 10 38 f2 74 0e f3 90 8a 10 <eb> f6 66 83 38 00 75 f4 eb e5 c3 8d 74 26 00 f0 81 28 00 00 00 
+0

顯然,消息意味着檢測到軟鎖定。你可以谷歌的是什麼意思。如果您想自己調試此問題(並要求提供幫助),則需要提供其他信息。如果你想要其他人進行調試,你需要向維護人員詢問。 – Tsyvarev

回答

0

一個softlockup被定義爲導致內核在 內核模式下超過20秒循環而不給其他任務有機會運行的錯誤。

日誌

kernel:BUG: soft lockup - CPU#30 stuck for 61s! [events/30:161] 

由下面的行中kernel/kernel/watchdog.c

pr_emerg("BUG: soft lockup - CPU#%d stuck for %us! [%s:%d]\n", 
     smp_processor_id(), 
     duration, 
     current->comm, 
     task_pid_nr(current)); 

產生這意味着

  • 該系統中的CPU core 30
  • 在過去的61秒內一直忙於執行內核代碼。
  • 系統上的當前線程爲events/30
  • 其進程ID爲161

有關詳細信息,結賬kernel/Documentation/lockup-watchdogs.txt