Date: Thu, 11 Oct 2018 22:35:14 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 202409] vm_thread_new: kstack allocation failed on FreeBSD 10.x Message-ID: <bug-202409-227-7h0VJ7ryo9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-202409-227@https.bugs.freebsd.org/bugzilla/> References: <bug-202409-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202409 Mikhail Teterin <mi@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mi@FreeBSD.org Severity|Affects Only Me |Affects Some People Version|10.0-RELEASE |11.2-STABLE --- Comment #1 from Mikhail Teterin <mi@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.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202409-227-7h0VJ7ryo9>