Public bug reported:
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?
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: bot-comment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839214
Title:
Setting vm.overcommit_kbytes = 0 made the entire system explode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1839214/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
