group.of.nepali.translators team mailing list archive

Thread
Date

[Bug 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>
Date: Thu, 19 Jan 2017 19:23:15 -0000
Reply-to: Bug 1630924 <1630924@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

I see commit 59107e2f4 in mainline:
59107e2f4883 x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic

However, I don't see 56ef6718a as of yet.  Do you have a patch
available?

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

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

** Changed in: linux (Ubuntu Vivid)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer -Force

  This case also applies to:
      -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
      -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
      -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

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