-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1
Hi,
I have got a lot of this in dmesg output for RELENG_7_0 as of today:
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
Any idea?
Cheers,

- --

Xin LI <delphij@delphij.net>	http://www.delphij.net/

FreeBSD - The Power to Serve!

-----BEGIN PGP SIGNATURE-----

Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFHloAci+vbBBjt66ARAl+8AJ9MR39A2x4ynKQ06BOKAWEaoJfBVQCgkwDg

jTeZCc0rALWjABp2wOBK2u0=

=YRAd

-----END PGP SIGNATURE-----

_______________________________________________

freebsd-current@freebsd.org mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-current

To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

Does it cause any problems aside from printing these messages ?

What workload do you put on the machine ?
The messages came from the failure of the kernel to allocate address

space for the kernel stack for a thread being created. Previously, the

system would panic encountering this situation.
This may happen due to kernel_map address space depletion, for instance,

by having a lot (on i386 machines with > 1Gb memory, ~40000) threads.

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1
It was an rsync from NFS to ZFS with ~15M of files, and rsync will

consume basically all physical memory.  I end up with some 2GB active,

4GB wired thing. (The system has 8GB of RAM), and I added a "make -j9
Yes, I knew, previously it just panic and hangs there, and thanks a lot
It seems that I have hit some sort of "leak" or some exhaustion issue.

Say, when the workload is gone, the system did not recover from the

situation, and reboot worked fine.
The system is sort of in production and it is about 20 miles away from

my office.  Do you want me to do some experiments for this?
Cheers,

- --

Xin LI <delphij@delphij.net>	http://www.delphij.net/

FreeBSD - The Power to Serve!

-----BEGIN PGP SIGNATURE-----

Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFHltfEi+vbBBjt66ARAi+yAKC3HKy9YaOHNZK3l45NUVYDxc5EZQCfWOlN

rTaCDmEc9ZZoizRRdcBOFF4=

=/tP1

-----END PGP SIGNATURE-----

_______________________________________________

freebsd-current@freebsd.org mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-current

To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

Yes, I want to know what exactly leaked. Ideally, I would like to see the

series of the output of the vmstat -z and vmstat -m for some time before

the system is bogged down. But, even the one snapshot of the vmstat -z/-m

output immediately before things stop working would be good to look at.
Output of the ps auxwwH is helpful too.