Date: Fri, 1 Sep 2006 13:50:38 -0700 From: "Kip Macy" <kip.macy@gmail.com> To: "Julian Elischer" <julian@elischer.org> Cc: Vyacheslav Vovk <vovk@km.ua>, freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: panic: vm_thread_new: kstack allocation failed Message-ID: <b1fa29170609011350s88b452cjfd939cbffe9d8029@mail.gmail.com> 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
On closer inspection this means that we've run out of KVA. In
principle it should be handled more gracefully, but the 1GB KVA
limitation is really a 32-bit artifact. It might be worth wading
through the kernel memory allocations to see if a subsystem has gone
beserk.
-Kip
On 9/1/06, Kip Macy <kip.macy@gmail.com> wrote:
> I've seen this when running stress2 with a large number of
> incarnations. Why don't we return an error to the user?
>
> -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"
> >
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170609011350s88b452cjfd939cbffe9d8029>