Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757762AbWK0KQD (ORCPT ); Mon, 27 Nov 2006 05:16:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757768AbWK0KQD (ORCPT ); Mon, 27 Nov 2006 05:16:03 -0500 Received: from mx2.suse.de ([195.135.220.15]:21679 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1757765AbWK0KQB (ORCPT ); Mon, 27 Nov 2006 05:16:01 -0500 From: Andi Kleen To: "Zhao Forrest" Subject: Re: Which patch fix the 8G memory problem on x64 platform? Date: Mon, 27 Nov 2006 11:15:55 +0100 User-Agent: KMail/1.9.5 Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611271115.55899.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 721 Lines: 20 On Monday 27 November 2006 11:02, Zhao Forrest wrote: > Hi Andi, > > The kernel 2.6.18.3 runs very well on my x64 server with 2 CPU's and > 8G memory; however kernel 2.6.16.32 kernel panic(Kernel panic - not > syncing: Attempted to kill init) under the stress test. After I use > mem=4000M for kernel 2.6.16.32, the kernel panic doesn't happen under > stress test. I'm not aware of a "8G memory problem" Best you write a full bug report and possibly git bisect it. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/