lkml.org 
[lkml]   [2001]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: a memory-related problem?
Probably what happens is that your BIOS stores some data in the top
megabyte of RAM, but doesn't set up the memory map to reflect this.
Therefore, Linux overwrites whatevers up there, causing problems.

On Sun, Jun 17, 2001 at 09:26:50PM +0200, Ronald Bultje wrote:
> P6b has three mem-slots. I would get "unresolved errors in init" if I
> had 2x64+1x128 sticks, and I would get oopses if I had 2x128M sticks. So
> there is indeed a weird difference.
> I just noticed this: if I supply "linux-2.4.4 mem=255M" instead of
> "linux-2.4.4 mem=256M" at the lilo prompt, it does work. Is this a bug
> in the code that handles options given at startup-time? (I only tried
> this for 2x128 sticks but I suppose this is the same for 2x64+1x128
> sticks - I guess I'm too lazy to try it out).
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:17    [W:0.057 / U:0.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site