group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #10489
[Bug 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10
** 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 नेपाली
भाषा समायोजकहरुको समूह, 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:
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