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

[Joseph Salisbury]

Hi Chris,

I removed Vivid from the bug.

** No longer affects: linux (Ubuntu Vivid)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Chris Valean]

Can we get Vivid out of the list please?
I see that it is now EOL.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-8.10

---
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
(LP: #1663687)
- scsi: storvsc: Enable tracking of queue depth
- scsi: storvsc: Remove the restriction on max segment size
- scsi: storvsc: Enable multi-queue support
- scsi: storvsc: use tagged SRB requests if supported by the device
- scsi: storvsc: properly handle SRB_ERROR when sense message is present
- scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
caused KVM host hung and all KVM guests down. (LP: #1651248)
- KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
- KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
- KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
(LP: #1531747)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
- SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
- SAUCE: md/raid6 algorithms: scale test duration for speedier boots
- SAUCE: Import aufs driver
- d-i: Build message-modules udeb for arm64
- rebase to v4.10-rc8

  * Miscellaneous upstream changes
- Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
- Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support 
setattr_prepare()"
- Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
- Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
- Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner   Mon, 06 Feb 2017 08:34:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1575

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1576

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-38.41

---
linux (4.8.0-38.41) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1661232

  * Backport Dirty COW patch to prevent wineserver freeze (LP: #1658270)
- SAUCE: mm: Respect FOLL_FORCE/FOLL_COW for thp

  * Kdump through NMI SMP and single core not working on Ubuntu16.10
(LP: #1630924)
- x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic
- SAUCE: hv: don't reset hv_context.tsc_page on crash

  * Call trace when testing fstat stressor on ppc64el with virtual  keyboard and
mouse present (LP: #1652132)
- HID: usbhid: Quirk a AMI virtual mouse and keyboard with ALWAYS_POLL

  * regression in linux-libc-dev in yakkety: C++ style comments are not allowed
in ISO C90 (LP: #1659654)
- generic syscalls: kill cruft from removed pkey syscalls

  * [16.04.2] POWER9 patches on top of 4.8 (LP: #1650263)
- powerpc/book3s: Add a cpu table entry for different POWER9 revs
- powerpc/mm/radix: Use different RTS encoding for different POWER9 revs
- powerpc/mm/radix: Use different pte update sequence for different POWER9
  revs
- powerpc/mm: Update the HID bit when switching from radix to hash
- powerpc/64/kexec: NULL check "clear_all" in kexec_sequence
- powerpc/64/kexec: Fix MMU cleanup on radix
- powerpc/mm: Add radix flush all with IS=3
- powerpc/64/kexec: Copy image with MMU off when possible
- powerpc/64: Simplify adaptation to new ISA v3.00 HPTE format
- powerpc/mm/radix: Invalidate ERAT on tlbiel for POWER9 DD1
- powerpc/mm: Fix missing update of HID register on secondary CPUs
- powerpc/64: Add some more SPRs and SPR bits for POWER9
- powerpc/64: Provide functions for accessing POWER9 partition table
- powerpc/powernv: Define real-mode versions of OPAL XICS accessors
- powerpc/64: Define new ISA v3.00 logical PVR value and PCR register value
- mm: update mmu_gather range correctly
- mm/hugetlb: add tlb_remove_hugetlb_entry for handling hugetlb pages
- mm: add tlb_remove_check_page_size_change to track page size change
- powerpc: Revert Load Monitor Register Support
- powerpc/mm: Correct process and partition table max size
- powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online
- powerpc/mm/radix: Setup AMOR in HV mode to allow key 0
- powerpc/mm: Detect instruction fetch denied and report
- powerpc/mm/radix: Prevent kernel execution of user space
- powerpc/mm: Rename hugetlb-radix.h to hugetlb.h
- powerpc/mm/hugetlb: Handle hugepage size supported by hash config
- powerpc/mm: Introduce _PAGE_LARGE software pte bits
- powerpc/mm: Add radix__tlb_flush_pte_p9_dd1()
- powerpc/mm: update radix__ptep_set_access_flag to not do full mm tlb flush
- powerpc/mm: update radix__pte_update to not do full mm tlb flush
- powerpc/mm: Batch tlb flush when invalidating pte entries
- powerpc/sparse: Make a bunch of things static
- powerpc/perf: factor out the event format field
- powerpc/perf: update attribute_group data structure
- powerpc/perf: power9 raw event format encoding
- powerpc/perf: macros for power9 format encoding
- KVM: PPC: Book3S: Don't crash if irqfd used with no in-kernel XICS 
emulation
- KVM: PPC: Implement kvm_arch_intc_initialized() for PPC
- KVM: PPC: Book3S HV: Move struct kvmppc_vcore from kvm_host.h to
  kvm_book3s.h
- KVM: PPC: Book3S HV: Change vcore element runnable_threads from 
linked-list
  to array
- KVM: Export kvm module parameter variables
- KVM: PPC: Book3S HV: Implement halt polling
- KVM: Add provisioning for ulong vm stats and u64 vcpu stats
- KVM: PPC: Implement existing and add new halt polling vcpu stats
- powerpc/mm: Speed up computation of base and actual page size for a HPTE
- powerpc: Add simple cache inhibited MMIO accessors
- KVM: PPC: Book3S HV: Convert kvmppc_read_intr to a C function
- KVM: PPC: select IRQ_BYPASS_MANAGER
- KVM: PPC: Book3S HV: Introduce kvmppc_passthru_irqmap
- powerpc/powernv: Provide facilities for EOI, usable from real mode
- KVM: PPC: Book3S HV: Enable IRQ bypass
- KVM: PPC: Book3S HV: Handle passthrough interrupts in guest
- KVM: PPC: Book3S HV: Complete passthrough interrupt in host
- KVM: PPC: Book3S HV: Dump irqmap in debugfs
- KVM: PPC: Book3S HV: Tunable to disable KVM IRQ bypass
- KVM: PPC: Book3S HV: Update irq stats for IRQs handled in real mode
- KVM: PPC: Book3S HV: Set server for passed-through interrupts
- KVM: PPC: Book3S HV: Counters for passthrough IRQ stats
- KVM: PPC: e500: Use kmalloc_array() in kvm_vcpu_ioctl_config_tlb()
- KVM: PPC: e500: Less function calls in kvm_vcpu_ioctl_config_tlb() after
  error detection
- KVM: PPC: e500: Delete an unnecessary initialisation in
  kvm_vcpu_ioctl_config_tlb()
- KVM: PPC: e500: 

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-63.84

---
linux (4.4.0-63.84) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1660704

  * Backport Dirty COW patch to prevent wineserver freeze (LP: #1658270)
- SAUCE: mm: Respect FOLL_FORCE/FOLL_COW for thp

  * Kdump through NMI SMP and single core not working on Ubuntu16.10
(LP: #1630924)
- x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic
- SAUCE: hv: don't reset hv_context.tsc_page on crash

  * [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer
Chromebook R11 (LP: #1630238)
- [Config] CONFIG_PINCTRL_CHERRYVIEW=y

  * Call trace when testing fstat stressor on ppc64el with virtual  keyboard and
mouse present (LP: #1652132)
- SAUCE: HID: usbhid: Quirk a AMI virtual mouse and keyboard with 
ALWAYS_POLL

  * VLAN SR-IOV regression for IXGBE driver (LP: #1658491)
- ixgbe: Force VLNCTRL.VFE to be set in all VMDq paths

  * "Out of memory" errors after upgrade to 4.4.0-59 (LP: #1655842)
- mm, page_alloc: convert alloc_flags to unsigned
- mm, compaction: change COMPACT_ constants into enum
- mm, compaction: distinguish COMPACT_DEFERRED from COMPACT_SKIPPED
- mm, compaction: simplify __alloc_pages_direct_compact feedback interface
- mm, compaction: distinguish between full and partial COMPACT_COMPLETE
- mm, compaction: abstract compaction feedback to helpers
- mm, oom: protect !costly allocations some more
- mm: consider compaction feedback also for costly allocation
- mm, oom, compaction: prevent from should_compact_retry looping for ever 
for
  costly orders
- mm, oom: protect !costly allocations some more for !CONFIG_COMPACTION
- mm, oom: prevent premature OOM killer invocation for high order request

  * Backport 3 patches to fix bugs with AIX clients using IBMVSCSI Target Driver
(LP: #1657194)
- SAUCE: ibmvscsis: Fix max transfer length
- SAUCE: ibmvscsis: fix sleeping in interrupt context
- SAUCE: ibmvscsis: Fix srp_transfer_data fail return code

  * NVMe: adapter is missing after abnormal shutdown followed by quick reboot,
quirk needed (LP: #1656913)
- nvme: apply DELAY_BEFORE_CHK_RDY quirk at probe time too

  * Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping
will stop working (LP: #1625318)
- PCI: Do any VF BAR updates before enabling the BARs
- PCI: Ignore BAR updates on virtual functions
- PCI: Update BARs using property bits appropriate for type
- PCI: Separate VF BAR updates from standard BAR updates
- PCI: Don't update VF BARs while VF memory space is enabled
- PCI: Remove pci_resource_bar() and pci_iov_resource_bar()
- PCI: Decouple IORESOURCE_ROM_ENABLE and PCI_ROM_ADDRESS_ENABLE
- PCI: Add comments about ROM BAR updating

  * Linux rtc self test fails in a VM under xenial (LP: #1649718)
- kvm: x86: Convert ioapic->rtc_status.dest_map to a struct
- kvm: x86: Track irq vectors in ioapic->rtc_status.dest_map
- kvm: x86: Check dest_map->vector to match eoi signals for rtc

  * Xenial update to v4.4.44 stable release (LP: #1658091)
- Input: xpad - use correct product id for x360w controllers
- Input: i8042 - add Pegatron touchpad to noloop table
- selftests: do not require bash to run netsocktests testcase
- selftests: do not require bash for the generated test
- mm: fix devm_memremap_pages crash, use mem_hotplug_{begin, done}
- ocfs2: fix crash caused by stale lvb with fsdlm plugin
- mm/hugetlb.c: fix reservation race when freeing surplus pages
- KVM: x86: fix emulation of "MOV SS, null selector"
- KVM: eventfd: fix NULL deref irqbypass consumer
- jump_labels: API for flushing deferred jump label updates
- KVM: x86: flush pending lapic jump label updates on module unload
- KVM: x86: add Align16 instruction flag
- KVM: x86: add asm_safe wrapper
- KVM: x86: emulate FXSAVE and FXRSTOR
- KVM: x86: Introduce segmented_write_std
- nl80211: fix sched scan netlink socket owner destruction
- USB: serial: kl5kusb105: fix line-state error handling
- USB: serial: ch341: fix initial modem-control state
- USB: serial: ch341: fix open error handling
- USB: serial: ch341: fix control-message error handling
- USB: serial: ch341: fix open and resume after B0
- Input: elants_i2c - avoid divide by 0 errors on bad touchscreen data
- i2c: print correct device invalid address
- i2c: fix kernel memory disclosure in dev interface
- xhci: fix deadlock at host remove by running watchdog correctly
- vme: Fix wrong pointer utilization in ca91cx42_slave_get
- mnt: Protect the mountpoint hashtable with mount_lock
- tty/serial: atmel_serial: BUG: stop DMA from transmitting in stop_tx
- sysrq: attach sysrq handler correctly for 32-bit kernel
- sysctl: Drop reference added by grab_header in 

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

[Chris Valean]

Verified the following proposed kernels and confirm this as fixed in:
On Gen1VM: 16.04.1 with 4.4.0-63.67
On both Gen1 and Gen2VM: 16.10 with 4.8.0-38.49

Thank you!

** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Joshua R. Poulson]

We will verify this fix is in.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Tim Gardner]

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Chris Valean]

Hi Joe,
The test kernels with the commits are looking fine, I was able to successfully 
trigger and complete a kdump over NMI.
Tested Xenial and Yakkety on WS2016 and WS2012R2.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Joseph Salisbury]

I built test kernels with these two commits.  The test kernels can be
downloaded from:

Xenial: http://kernel.ubuntu.com/~jsalisbury/lp1630924/xenial/
Yakkey: http://kernel.ubuntu.com/~jsalisbury/lp1630924/yakkety
Zesty: http://kernel.ubuntu.com/~jsalisbury/lp1630924/zesty

The Vivid test kernel for 14.04.5(kernel: 3.19.0-69-generic) needs some
backporting, so I'll post that shortly.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Joseph Salisbury]

** No longer affects: linux (Ubuntu Vivid)

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
   Status: Confirmed

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

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

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

** Changed in: linux (Ubuntu Yakkety)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Confirmed => In Progress

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

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Chris Valean]

Haven't checked mainline, but it is in upstream. Please find it here -
http://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=56ef6718a

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Joseph Salisbury]

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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Chris Valean]

Please build a test kernel with these 2 commits:
59107e2f48831daedc46973ce4988605ab066de3
56ef6718a1d8d77745033c5291e025ce18504159

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Joseph Salisbury]

Do we happen to know what commits(Other than 69973b8308) are in 4.9 and
newer that are also needed in 4.8?

Do you want me to build a Yakkety test kernel with commit 69973b8308?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Chris Valean]

I did re-verify this now with the 4.9 mainline and kdump through NMI works fine.
There might have been additional patches and there is at least one other commit 
in upstream, however that one is addressing only x86 arch.

Full version info: v4.9 mainline build
v4.9 (69973b830859bc6529a7a0468ba0d80ee5117826)

Changing tag flag kernel-fixed-upstream

** Tags added: kernel-fixed-upstream

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Chris Valean]

Hi Joe,

I did verify this again with the below kernels and results:
- 4.8.0-22 16.10 kernel - kdump through NMI on 4 CPU cores doesn't work - VM 
gets stuck and there is no crash file nor a reboot.
- 4.9.0-040900RC8 kernel from ubuntu mainline - kdump through NMI works fine 
when using single core or SMP *with 4 cores*.
Using 8 cores on this kernel, triggering the crash will result in the same bad 
behavior as from the GA kernel. I don't see any crash messages on the console, 
and the VM will just hang. Will have to do more debugging on this new pattern.

All tests have been done with crashkernel=512M and 2GB RAM for the VM.

4.9 also just got released, as of 11/12.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Joseph Salisbury]

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

** Tags added: kernel-da-key kernel-hyper-v

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Chris Valean]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp