From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LNpLD-0008WV-Cs for garchives@archives.gentoo.org; Fri, 16 Jan 2009 14:06:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CDF14E070F; Fri, 16 Jan 2009 14:06:28 +0000 (UTC) Received: from spunkymail-a1.g.dreamhost.com (sd-green-bigip-81.dreamhost.com [208.97.132.81]) by pigeon.gentoo.org (Postfix) with ESMTP id 9C318E070F for ; Fri, 16 Jan 2009 14:06:28 +0000 (UTC) Received: from [192.168.69.3] (142.Red-83-40-249.dynamicIP.rima-tde.net [83.40.249.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by spunkymail-a1.g.dreamhost.com (Postfix) with ESMTP id 4CEBFFE1D7 for ; Fri, 16 Jan 2009 06:06:26 -0800 (PST) Message-ID: <49709459.5020908@hiramoto.org> Date: Fri, 16 Jan 2009 15:06:17 +0100 From: Karl Hiramoto User-Agent: Thunderbird 2.0.0.19 (X11/20090102) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-server@lists.gentoo.org Reply-to: gentoo-server@lists.gentoo.org MIME-Version: 1.0 To: gentoo-server@lists.gentoo.org Subject: Re: [gentoo-server] Kernel crash References: <20090116012319.O96190@shell.bway.net> In-Reply-To: <20090116012319.O96190@shell.bway.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: c03b9d4f-a610-487e-9c6f-44126c7451a1 X-Archives-Hash: 411ca3d9ee6a59c6584e7b2a231e7b27 Ajai Khattri wrote: > > Ive has problems recently with a production web server crashing at > rando times. So far Ive been unable to find the culprit. Kernel is > pretty recent 2.6.25 and the rest of software has been running fine > (hasn't been changed). > --- > The kernel made it to a BUG() call . Try upgrading to 2.6.28.. Bugs in old kernels in general are not fixed. 2.6.28.1 may be out soon and in that case try that. If the problem persists you should report it again. -- Karl Hiramoto