*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
** This bug has been marked a duplicate of bug 1741934
Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix)
--
You received this bug notification because you are a member of
I cannot boot system on a desktop computer, not virtual. I need press reset
buton to resart freeze system.
I've a i5-4460 processor. I've returned to 4.4.0-104 generic kernel to restart
my computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can you see if this bug happens with the following kernel:
http://kernel.ubuntu.com/~jsalisbury/lp1741934/
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
For what it's worth, a similar setup but using an AMD CPU (C-60) has no
problem with nmi_watchdog=0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742286
Title:
[regression] Xenial host with
After multiple reboots, it turns out that the problematic host's boot
arg is "nmi_watchdog=0".
If I set the host with only those:
sdeziel@xeon:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic
root=UUID=40a302c9-82d9-4574-ac2f-efcf5c9d126f ro hugepages=3008 kaslr
possible_cpus=2
xeon is the host/hypervisor and it has the following boot args:
sdeziel@xeon:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic
root=UUID=40a302c9-82d9-4574-ac2f-efcf5c9d126f ro hugepages=3008 kaslr
nmi_watchdog=0 possible_cpus=2 transparent_hugepage=never vsyscall=none
The
