From owner-freebsd-threads@FreeBSD.ORG  Fri Sep  1 16:27:17 2006
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
X-Original-To: freebsd-threads@freebsd.org
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EA6D216A4DA;
	Fri,  1 Sep 2006 16:27:17 +0000 (UTC)
	(envelope-from prvs=julian=392b3a9d5@elischer.org)
Received: from a50.ironport.com (a50.ironport.com [63.251.108.112])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BE94143D58;
	Fri,  1 Sep 2006 16:27:16 +0000 (GMT)
	(envelope-from prvs=julian=392b3a9d5@elischer.org)
Received: from unknown (HELO [192.168.2.3]) ([10.251.60.33])
	by a50.ironport.com with ESMTP; 01 Sep 2006 09:27:16 -0700
Message-ID: <44F85F63.5020508@elischer.org>
Date: Fri, 01 Sep 2006 09:27:15 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.13) Gecko/20060414
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vyacheslav Vovk <vovk@km.ua>
References: <200609011716.30749.vovk@km.ua>
In-Reply-To: <200609011716.30749.vovk@km.ua>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org
Subject: Re: panic: vm_thread_new: kstack allocation failed
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2006 16:27:18 -0000

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
>
>  
>