From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 16:35:20 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D14516A4CE for ; Fri, 30 Jul 2004 16:35:20 +0000 (GMT) Received: from mail.revolutionsp.com (ganymede.revolutionsp.com [64.246.0.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB39943D1D for ; Fri, 30 Jul 2004 16:35:19 +0000 (GMT) (envelope-from klr@6s-gaming.com) Received: from mail.revolutionsp.com (localhost [127.0.0.1]) by mail.revolutionsp.com (Postfix) with ESMTP id 24AFA15C95 for ; Fri, 30 Jul 2004 13:32:44 +0000 (GMT) Received: from 81.84.175.12 (SquirrelMail authenticated user klr@6s-gaming.com); by mail.revolutionsp.com with HTTP; Fri, 30 Jul 2004 13:32:44 -0000 (GMT) Message-ID: <49388.81.84.175.12.1091194364.squirrel@81.84.175.12> Date: Fri, 30 Jul 2004 13:32:44 -0000 (GMT) From: "Hugo Silva" To: freebsd-hackers@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: 5.2.1-p9 SMP kernel panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 16:35:20 -0000 Hi, I am getting a panic on a 5.2.1-p9 Dual Xeon 3.0ghz w/ SMP enabled. The panic always happens during high loads (create a new jail, compile something, etc) I know another user had this problem a while ago, and adding an option to the kernel solved his problem. But I can't locate this thread (could by freebsd-archives, but doesnt contain the reply I saw the last time, must have read it somewhere else) Does anyone know what is the magic option I have to add to the kernel to prevent these panics? I can't give details about the panic (datacenter still didn't mail me a copy of the text), but I'm pretty sure it's due to high loads -- I stopped seti@home and let the server idle, it's been up for 3 days when it wouldn't be up for more than 24 hours. Thanks in advance! Hugo -- www.6s-gaming.com