From owner-freebsd-stable@FreeBSD.ORG Mon Jun 5 19:14:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C98516A5EA for ; Mon, 5 Jun 2006 19:14:57 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8000F43D45 for ; Mon, 5 Jun 2006 19:14:56 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id B464E5E79; Mon, 5 Jun 2006 15:14:55 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HwKyJtx0eHyE; Mon, 5 Jun 2006 15:14:54 -0400 (EDT) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id CF6F45E11; Mon, 5 Jun 2006 15:14:54 -0400 (EDT) In-Reply-To: <04E7E1FC-4408-4808-B5BC-18DE60249185@aros.net> References: <04E7E1FC-4408-4808-B5BC-18DE60249185@aros.net> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3AAF07F5-1C7C-4F7E-A9D0-A8AD69C48490@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 5 Jun 2006 15:14:51 -0400 To: Lonnie Olson X-Mailer: Apple Mail (2.750) Cc: freebsd-stable@freebsd.org Subject: Re: Requesting advice for panic: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2006 19:14:58 -0000 On Jun 5, 2006, at 2:00 PM, Lonnie Olson wrote: > I have been fighting this issue for months now. I am about to give > up and go back to FreeBSD 4.x. I am looking for suggestions now. > > 1. What does this panic really mean? I believe it implies that the kernel address space is exhausted, so when something tried to start up a new kthread, this failed because the kernel does not have enough memory to allocate a new stack for that thread. > 2. Any ideas for a work around? (kernel options, patches, anything) Set up a cron job to run "sysctl kern.malloc > /var/tmp/kern_malloc" every minute or whatnot, and take a look at the last entry you get before the machine panics. That will help identify what is running your kernel out of memory. > 3. Would a bug report actually get anywhere? (bad experiences in > the past, 93809) Maybe. You'll need to provide more information than just a dmesg, but even if you don't get a specific solution to your problem in the short term, having things in the PR database will help over the long term... -- -Chuck