Joe,
116 puts VMWARE into a loop. It forces a hard reboot somewhere during
the init process (scrolls by too fast). If I had NOPTI it boots
normally. So I would say, no, 116 does not fix this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
Overnight I had 2 of 12 16.04 servers brick with the 108 kernel. They
also do not work with 109. They work fine with 104. The other 10 worked
fine on both 108 and 109.
All are hosted on VMWARE. The two broken ones stop at the same place. I
was able to go back to the 104 ker
booting on 109 with nopti works! Good call Leann.
--
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/1742502
Title:
108 and 109 kernel hangs
Status in linux package in Ubuntu:
Triaged
Sta
Additional info in hopes it proves useful.
On the hung boots, there is no recorded output to disk unfortunately.
This is what's installed on the machine running 108 nopti:
jstanford@www:~$ dpkg -l linux* |grep ii
ii linux-base 4.0ubuntu1all Linux image
base
112 kernel has the same issue. Adding nopti allows it to boot.
What's different: It stops after zswap loading.
--
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/1742502
Title:
108 and 109
5 matches
Mail list logo
