linux-mips
[Top] [All Lists]

Re: 'mem= ' Kernel Boot Parameter on BCM1250/1480 Platform

To: Gary Smith <gary.smith@3phoenix.com>
Subject: Re: 'mem= ' Kernel Boot Parameter on BCM1250/1480 Platform
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Thu, 29 Mar 2007 20:53:17 +0100 (BST)
Cc: linux-mips@linux-mips.org
In-reply-to: <001301c77234$04d014c0$8eacaac0@3PiGAS>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <001301c77234$04d014c0$8eacaac0@3PiGAS>
Sender: linux-mips-bounce@linux-mips.org
On Thu, 29 Mar 2007, Gary Smith wrote:

> I'd like to ask a question about use of the 'mem=' kernel parameter.  When
> booting without this parameter, the kernel automatically detects the amount
> of memory as 989020 kB.  If a kernel parameter is added to specify
> 'mem=989020k' a TLB Miss error is encountered.  Do you all have guidance
> about how the memory parameter can be specified without causing the error?
> Since the mem= parameter was set to an identical value as the memory
> reported by meminfo in the /proc filesystem, use of this kernel parameter
> should be OK.  This behavior has been observed on both the BCM1250/1480
> platforms when running Debian linux.  The 2.6.17-2 kernel is used with the
> system.

 Make sure the overridden ranges as reported in the "User-defined physical 
RAM map" dump do not claim any reserved areas reported in the "Determined 
physical RAM map" dump at the beginning of the bootstrap.

  Maciej

<Prev in Thread] Current Thread [Next in Thread>