From owner-freebsd-stable@FreeBSD.ORG Mon Jun 5 18:00:09 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 15C7A16B223 for ; Mon, 5 Jun 2006 18:00:08 +0000 (UTC) (envelope-from fungus@aros.net) Received: from ceres.aros.net (ceres.aros.net [66.219.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 452C243D49 for ; Mon, 5 Jun 2006 18:00:08 +0000 (GMT) (envelope-from fungus@aros.net) Received: from [10.0.1.28] (firebat.aros.net [66.219.192.36]) by ceres.aros.net (8.13.3/8.13.3) with ESMTP id k55I07bP022930 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Mon, 5 Jun 2006 12:00:07 -0600 (MDT) (envelope-from fungus@aros.net) Mime-Version: 1.0 (Apple Message framework v750) To: freebsd-stable@freebsd.org Message-Id: <04E7E1FC-4408-4808-B5BC-18DE60249185@aros.net> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2--575486184; protocol="application/pkcs7-signature" From: Lonnie Olson Date: Mon, 5 Jun 2006 12:00:05 -0600 X-Mailer: Apple Mail (2.750) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on ceres.aros.net X-Virus-Status: Clean X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 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 18:00:28 -0000 --Apple-Mail-2--575486184 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I currently have a problem that others have had before, but no one actually did anything to explain or help. I have a mail server that is often under high load. It panics about every day or two with "vm_thread_new: kstack allocation failed". I have a dump, but I doubt it is necessary as the details of this problem have been documented many times before. threads/80435: panic on high loads http://lists.freebsd.org/pipermail/freebsd-threads/2005-April/ 003025.html No resolution because reporter wasn't running -STABLE. panic: vm_thread_new: kstack allocation failed http://lists.freebsd.org/pipermail/freebsd-current/2006-March/ 061544.html No discussion about it other than testing methods. FreeBSD 5.4-P12 Panic "vm_thread_new: kstack allocation failed" under load http://lists.freebsd.org/pipermail/freebsd-questions/2006-March/ 116290.html Just a "pass the buck" comment about upgrading to 6.1 I *am* running 6-STABLE. I have had this particular panic since 5.4- RELEASE. I am using an SMP kernel with only this change to fix a different kernel panic before. options VM_KMEM_SIZE_MAX=419430400 The machine is a dual AMD Opteron w/ 2G memory. I have another identical machine that this also occurs on but less frequently as it does not have as high of a load. I have tested every piece of hardware as best as I can, especially the memory. 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? 2. Any ideas for a work around? (kernel options, patches, anything) 3. Would a bug report actually get anywhere? (bad experiences in the past, 93809) --Apple-Mail-2--575486184--