From owner-freebsd-threads@FreeBSD.ORG Fri Sep 1 20:50:46 2006 Return-Path: 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 CF9B516A512 for ; Fri, 1 Sep 2006 20:50:46 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D31843D6B for ; Fri, 1 Sep 2006 20:50:39 +0000 (GMT) (envelope-from kip.macy@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so623893nzn for ; Fri, 01 Sep 2006 13:50:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lP0NsDqZWqXZ6lr9okkGfdUAopMgR+2tdFOpjcYjmjVNSKMwU8TbTmtOfL2WIOGSHdTaw/pezaPPkg9Ytm9rfhmbmwqS7IONWDQQnoXhIXy0ipbPPcsPiqf1ZEhROVfKkik+caMwZ69eMSPezoqE2AGjtyOpRgpdixAm9bR9m38= Received: by 10.65.211.13 with SMTP id n13mr3250659qbq; Fri, 01 Sep 2006 13:50:38 -0700 (PDT) Received: by 10.65.224.1 with HTTP; Fri, 1 Sep 2006 13:50:38 -0700 (PDT) Message-ID: Date: Fri, 1 Sep 2006 13:50:38 -0700 From: "Kip Macy" To: "Julian Elischer" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200609011716.30749.vovk@km.ua> <44F85F63.5020508@elischer.org> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 20:50:46 -0000 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 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 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" > > >