Date: Wed, 23 Jan 2008 07:12:15 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: d@delphij.net Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: RELENG_7_0: vm_thread_new: kstack allocation failed Message-ID: <20080123051215.GU57756@deviant.kiev.zoral.com.ua> In-Reply-To: <4796801C.7010601@delphij.net> References: <4796801C.7010601@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--DpucUjQmhxB+SJDU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 22, 2008 at 03:45:32PM -0800, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Hi, >=20 > I have got a lot of this in dmesg output for RELENG_7_0 as of today: >=20 > 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 >=20 > Any idea? 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. --DpucUjQmhxB+SJDU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkeWzK4ACgkQC3+MBN1Mb4g2JwCeLauj/eM4Puvet6eJpw+VkNfH DyEAoMzuW0LM2hklvW69Y9xCKQzVxxIU =EirA -----END PGP SIGNATURE----- --DpucUjQmhxB+SJDU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080123051215.GU57756>