← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1908428] [NEW] 4.4 kernel panics in kvm wake_up() handler

 

Public bug reported:

User reported that 4.4 kernels are affected by the bug in [1].

The bug presents itself with the following trace :

[219901.424329] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G           OE   4.4.0-133-generic #159~14.04.1-Ubuntu
[219901.441800] task: ffff885f62e63fc0 ti: ffff885f62e7c000 task.ti: ffff885f62e7c000
[219901.449408] RIP: 0010:[<ffffffffc09c8cfd>]  [<ffffffffc09c8cfd>] wakeup_handler+0x6d/0xa0 [kvm_intel]
[219901.458791] RSP: 0018:ffff885f7c043f70  EFLAGS: 00010083
[219901.464217] RAX: ffff885f7c040000 RBX: dead0000000000b8 RCX: ffff885f7c0586c0
[219901.471480] RDX: dead000000000100 RSI: 0000000000000000 RDI: ffff885f7c0586b0
[219901.478741] RBP: ffff885f7c043f90 R08: 0000000000000000 R09: 0000c7ffc2ec9069
[219901.486003] R10: 0000000000000494 R11: ffff885f7c057370 R12: 00000000000186b0
[219901.493267] R13: 0000000000000013 R14: 00000000000186c0 R15: ffff885f62e7c000
[219901.500528] FS:  0000000000000000(0000) GS:ffff885f7c040000(0000) knlGS:0000000000000000
[219901.511738] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[219901.517597] CR2: 00007f6d57098000 CR3: 0000003183dfe000 CR4: 0000000000362670
[219901.524860] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[219901.532121] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[219901.539384] Stack:
[219901.541509]  0000000000000000 0000000000000013 0000000000000000 0000000000000000
[219901.549120]  ffff885f7c043fa8 ffffffff8102fa99 ffffffff81f40200 ffff885f62e7fe98
[219901.556747]  ffffffff8182131f ffff885f62e7fde8 <EOI>  ffff885f62e7c000 0000000000000000
[219901.565006] Call Trace:
[219901.567567]  <IRQ> 
[219901.569592]  [<ffffffff8102fa99>] smp_kvm_posted_intr_wakeup_ipi+0x59/0x70
[219901.576795]  [<ffffffff8182131f>] kvm_posted_intr_wakeup_ipi+0xbf/0xd0
[219901.583431]  <EOI> 
[219901.585456]  [<ffffffff81037b30>] ? hard_disable_TSC+0x30/0x30
[219901.591621]  [<ffffffff810645a6>] ? native_safe_halt+0x6/0x10
[219901.597479]  [<ffffffff81037b4e>] default_idle+0x1e/0xe0
[219901.602900]  [<ffffffff810386c5>] arch_cpu_idle+0x15/0x20
[219901.608416]  [<ffffffff810c3e7a>] default_idle_call+0x2a/0x40
[219901.614270]  [<ffffffff810c41d0>] cpu_startup_entry+0x2e0/0x350
[219901.620305]  [<ffffffff81050c2c>] start_secondary+0x16c/0x190


The root cause is blocked_vcpu_on_cpu list is corrupted.
This bug is fixed  with the patchset found in [2].
Only the first 3 (out of 4) of them have made their way in upstream kernel and 
are the ones needed to fix the bug.

A test kernel with the fixing patches have been provided to the user and they
confirmed that it resolves the issue.

[1] https://marc.info/?l=kvm&m=149559827906211&w=2
[2] https://lore.kernel.org/lkml/20170606105707.23207-1-pbonzini@xxxxxxxxxx/

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1908428

Title:
  4.4 kernel panics in kvm wake_up() handler

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  User reported that 4.4 kernels are affected by the bug in [1].

  The bug presents itself with the following trace :

  [219901.424329] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G           OE   4.4.0-133-generic #159~14.04.1-Ubuntu
  [219901.441800] task: ffff885f62e63fc0 ti: ffff885f62e7c000 task.ti: ffff885f62e7c000
  [219901.449408] RIP: 0010:[<ffffffffc09c8cfd>]  [<ffffffffc09c8cfd>] wakeup_handler+0x6d/0xa0 [kvm_intel]
  [219901.458791] RSP: 0018:ffff885f7c043f70  EFLAGS: 00010083
  [219901.464217] RAX: ffff885f7c040000 RBX: dead0000000000b8 RCX: ffff885f7c0586c0
  [219901.471480] RDX: dead000000000100 RSI: 0000000000000000 RDI: ffff885f7c0586b0
  [219901.478741] RBP: ffff885f7c043f90 R08: 0000000000000000 R09: 0000c7ffc2ec9069
  [219901.486003] R10: 0000000000000494 R11: ffff885f7c057370 R12: 00000000000186b0
  [219901.493267] R13: 0000000000000013 R14: 00000000000186c0 R15: ffff885f62e7c000
  [219901.500528] FS:  0000000000000000(0000) GS:ffff885f7c040000(0000) knlGS:0000000000000000
  [219901.511738] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
  [219901.517597] CR2: 00007f6d57098000 CR3: 0000003183dfe000 CR4: 0000000000362670
  [219901.524860] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
  [219901.532121] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
  [219901.539384] Stack:
  [219901.541509]  0000000000000000 0000000000000013 0000000000000000 0000000000000000
  [219901.549120]  ffff885f7c043fa8 ffffffff8102fa99 ffffffff81f40200 ffff885f62e7fe98
  [219901.556747]  ffffffff8182131f ffff885f62e7fde8 <EOI>  ffff885f62e7c000 0000000000000000
  [219901.565006] Call Trace:
  [219901.567567]  <IRQ> 
  [219901.569592]  [<ffffffff8102fa99>] smp_kvm_posted_intr_wakeup_ipi+0x59/0x70
  [219901.576795]  [<ffffffff8182131f>] kvm_posted_intr_wakeup_ipi+0xbf/0xd0
  [219901.583431]  <EOI> 
  [219901.585456]  [<ffffffff81037b30>] ? hard_disable_TSC+0x30/0x30
  [219901.591621]  [<ffffffff810645a6>] ? native_safe_halt+0x6/0x10
  [219901.597479]  [<ffffffff81037b4e>] default_idle+0x1e/0xe0
  [219901.602900]  [<ffffffff810386c5>] arch_cpu_idle+0x15/0x20
  [219901.608416]  [<ffffffff810c3e7a>] default_idle_call+0x2a/0x40
  [219901.614270]  [<ffffffff810c41d0>] cpu_startup_entry+0x2e0/0x350
  [219901.620305]  [<ffffffff81050c2c>] start_secondary+0x16c/0x190

  
  The root cause is blocked_vcpu_on_cpu list is corrupted.
  This bug is fixed  with the patchset found in [2].
  Only the first 3 (out of 4) of them have made their way in upstream kernel and 
  are the ones needed to fix the bug.

  A test kernel with the fixing patches have been provided to the user and they
  confirmed that it resolves the issue.

  [1] https://marc.info/?l=kvm&m=149559827906211&w=2
  [2] https://lore.kernel.org/lkml/20170606105707.23207-1-pbonzini@xxxxxxxxxx/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908428/+subscriptions


Follow ups