Date: Fri, 01 Sep 2006 13:03:36 -0700 From: Julian Elischer <julian@elischer.org> To: Kip Macy <kip.macy@gmail.com> Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: panic: vm_thread_new: kstack allocation failed Message-ID: <44F89218.9050400@elischer.org> In-Reply-To: <b1fa29170609011218m1f4eb3ebpafb0365fe2748a45@mail.gmail.com> References: <200609011716.30749.vovk@km.ua> <44F85F63.5020508@elischer.org> <b1fa29170609011218m1f4eb3ebpafb0365fe2748a45@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kip Macy wrote: > I've seen this when running stress2 with a large number of > incarnations. Why don't we return an error to the user? programmer ENOTIME patch welcome! > > -Kip > > On 9/1/06, Julian Elischer <julian@elischer.org> wrote: > >> Vyacheslav Vovk wrote: >> >> can you see how many threads thre are in the system? >> I think you will have to extract this information frome the zone >> allocator. >> >> I just realised there is no effective limit on kernel threads in the >> system. >> probably one could cause this with a fork bomb appoach using forks and >> thread creation. >> >> >Unread portion of the kernel message buffer: >> >panic: vm_thread_new: kstack allocation failed >> >cpuid = 3 >> >Uptime: 7d4h30m58s >> > >> > >> > >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to > "freebsd-threads-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44F89218.9050400>