From: Ronald Bultje <rbultje@ronald.bitfreak.net>
To: klink@clouddancer.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: a memory-related problem?
Date: 17 Jun 2001 21:26:50 +0200 [thread overview]
Message-ID: <992806021.2007.0.camel@tux.bitfreak.net> (raw)
In-Reply-To: <20010617131002.EF84D784BD@mail.clouddancer.com>
In-Reply-To: <CDEJIPDFCLGDNEHGCAJPOEFGCCAA.rbultje@ronald.bitfreak.net> <9gi848$pb2$1@ns1.clouddancer.com> <20010617131002.EF84D784BD@mail.clouddancer.com>
On 17 Jun 2001 06:10:02 -0700, Colonel wrote:
> In clouddancer.list.kernel, you wrote:
> >
> >Hi,
> >
> >I just added 128 MB of RAM to my machine which already had 128 MB and
> >which has 128 MB swap. 128 MB RAM + 128 MB swap (either the new or the
> >old 128 MB RAM) works, but the combination of that, 256 MB RAM + 128 MB
> >swap, crashes the compu during startup with either an "unresolved-
> >symbols in init" message (which is completely random, each boot shows
> >different unresolved references) or with oopses right after starting
> >init.
>
> It's more likely that the two RAM sticks differ. I had a similar
> problem in a Windoze machine awhile ago. Move one stick of RAM into
> another bank, i.e. with 4 memory slots, use #1 and #3. If you only
> have 2 memory slots, return/sell what you have and buy 2 sticks at the
> same time.
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).
Regards,
Ronald Bultje
next prev parent reply other threads:[~2001-06-17 17:36 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 [this message]
2001-06-17 17:53 ` Steven Walter
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=992806021.2007.0.camel@tux.bitfreak.net \
--to=rbultje@ronald.bitfreak.net \
--cc=klink@clouddancer.com \
--cc=linux-kernel@vger.kernel.org \
/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