From: Steven Walter <srwalter@yahoo.com>
To: Ronald Bultje <rbultje@ronald.bitfreak.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a memory-related problem?
Date: Sun, 17 Jun 2001 12:53:15 -0500 [thread overview]
Message-ID: <20010617125315.A24430@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <CDEJIPDFCLGDNEHGCAJPOEFGCCAA.rbultje@ronald.bitfreak.net> <9gi848$pb2$1@ns1.clouddancer.com> <20010617131002.EF84D784BD@mail.clouddancer.com> <992806021.2007.0.camel@tux.bitfreak.net>
In-Reply-To: <992806021.2007.0.camel@tux.bitfreak.net>; from rbultje@ronald.bitfreak.net on Sun, Jun 17, 2001 at 09:26:50PM +0200
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
next prev parent reply other threads:[~2001-06-17 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-17 12:37 a memory-related problem? Ronald Bultje
[not found] ` <9gi848$pb2$1@ns1.clouddancer.com>
2001-06-17 13:10 ` Colonel
2001-06-17 19:26 ` Ronald Bultje
2001-06-17 17:53 ` Steven Walter [this message]
2001-06-17 17:57 ` Alan Cox
2001-06-17 22:53 ` Andreas Bombe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010617125315.A24430@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rbultje@ronald.bitfreak.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox