Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751071AbWCZSlZ (ORCPT ); Sun, 26 Mar 2006 13:41:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751119AbWCZSlZ (ORCPT ); Sun, 26 Mar 2006 13:41:25 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:41157 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S1751071AbWCZSlY (ORCPT ); Sun, 26 Mar 2006 13:41:24 -0500 Date: Sun, 26 Mar 2006 20:40:49 +0200 (MEST) From: Jan Engelhardt To: "Randy.Dunlap" cc: jzb@aexorsyst.com, linux-kernel@vger.kernel.org Subject: Re: mem= causes oops In-Reply-To: <20060326094121.9464762a.rdunlap@xenotime.net> Message-ID: References: <200603212005.58274.jzb@aexorsyst.com> <200603240936.13178.jzb@aexorsyst.com> <20060324163237.5743bd3c.rdunlap@xenotime.net> <200603251036.40379.jzb@aexorsyst.com> <20060326094121.9464762a.rdunlap@xenotime.net> 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: 643 Lines: 18 >> >> Hm, seeing this mail reminds me of something I seen on SPARC just a while >> ago. Maybe it's just something on my side. If I specify `mem=65536`, that >> is, with no size suffix like M or G, what does Linux make out of it? 65536 >> KB or 64 KB? > >65536 bytes. All of the suffixes [KMG] are optional. > Oh ok, that should explain why it 'segfaults' with mem=65536 ;) Jan Engelhardt -- - 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/