This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1839214
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1839214
Title:
Setting vm.overcommit_kbytes = 0 made the entire system explode.
Status in linux package in Ubuntu:
Incomplete
Bug description:
On Ubuntu 16.04 LTS and the newest kernel 4.4.0-157, I tried the following
command:
echo "vm.overcommit_memory = 2" >> /etc/sysctl.conf
echo "vm.overcommit_kbytes = 0" >> /etc/sysctl.conf
sysctl -p
Then I can't reboot, all the commands are invalid, the system
explodes. After a forced restart, I can't even connect it with ssh.
#reboot
reboot -bash: fork: Cannot allocate memory
After some searching and inspection, I find the default value of
vm.overcommit_kbytes is 0, so why set it to 0 again will get such a
result?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839214/+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
