From owner-freebsd-hackers@freebsd.org Wed Jul 15 05:35:40 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8FB399CA3D for ; Wed, 15 Jul 2015 05:35:40 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C235B1D1A for ; Wed, 15 Jul 2015 05:35:40 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-240-47.lns20.per4.internode.on.net [121.45.240.47]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t6F5ZZvM078627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 14 Jul 2015 22:35:38 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <55A5F121.2070702@freebsd.org> Date: Wed, 15 Jul 2015 13:35:29 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Raviprakash Darbha , freebsd-hackers , "freebsd-hackers@freebsd.org" Subject: Re: vm.kmem_size setting for kstack allocation failure References: <9956D08B-2609-4AA2-AD62-721B753F6BFA@juniper.net> In-Reply-To: <9956D08B-2609-4AA2-AD62-721B753F6BFA@juniper.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2015 05:35:41 -0000 On 7/15/15 3:59 AM, Raviprakash Darbha wrote: > Hello All > > I have been working on a panic due to kernel stack allocation failure. vm_thread_new: kstack allocation failed > I understand that this could be a kmem_size setting problem where too less space is left for the stack. > > Any thoughts on setting vm.kmem_size to a lesser value ? more information is needed. what OS rev, hardware, etc. > > Thanks > Ravi > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > >