Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 8 Jul 2002 10:41:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 8 Jul 2002 10:41:49 -0400 Received: from pD952ABA4.dip.t-dialin.net ([217.82.171.164]:58325 "EHLO hawkeye.luckynet.adm") by vger.kernel.org with ESMTP id ; Mon, 8 Jul 2002 10:41:49 -0400 Date: Mon, 8 Jul 2002 08:44:27 -0600 (MDT) From: Thunder from the hill X-X-Sender: thunder@hawkeye.luckynet.adm To: Matthias Fricke cc: linux-kernel@vger.kernel.org Subject: Re: Kernel Ooops In-Reply-To: <3D29A2D9.CD8936DB@onetel.net.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1159 Lines: 35 Hi, On Mon, 8 Jul 2002, Matthias Fricke wrote: > Hallo, Obviously a german. > I am using 2.4.18 Kernel on a 512MB RAM Mashine. Kernel detects only 256 > MB. If I am booting lilo with mem=512M the kernel Ooopses and panics. > > The kernel is patched with kernel patch of kernel.org from februar 18 > th. > > Your documentation told me that memory assigment problems should have > gone with 2.4 kernels. So I think maybe it is really a problem. Have you tried the latest 2.4.19 yet? It _might_ help a bit (I'm not into 2.4 kernels, but I guess it might be different for later kernels). Regards, Thunder -- (Use http://www.ebb.org/ungeek if you can't decode) ------BEGIN GEEK CODE BLOCK------ Version: 3.12 GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$ N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G e++++ h* r--- y- ------END GEEK CODE BLOCK------ - 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/