[Bug 202409] vm_thread_new: kstack allocation failed on FreeBSD 10.x
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Oct 11 22:35:16 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202409
Mikhail Teterin <mi at FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mi at FreeBSD.org
Severity|Affects Only Me |Affects Some People
Version|10.0-RELEASE |11.2-STABLE
--- Comment #1 from Mikhail Teterin <mi at FreeBSD.org> ---
I'm having this problem now, with 11.2-STABLE r338668. My machine is, actually,
a guest VM. Memory is 8GB, but the OS i386 using PAE.
The role of forkbomb in my case is played by ansible -- which forks off
multiple processes for each of the hosts in the inventory.
Once the message starts appearing, the only "fix" is to reboot -- the problem
remains even after ansible exits. The relevant dmesg is:
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
[...]
There is no swap configured, but top reports ample free RAM:
Mem: 536M Active, 828M Inact, 141M Wired, 60M Buf, 6529M Free
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list