From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: BUG?: G5 not using all available memory -- SOLVED
Date: Tue, 22 Jun 2004 11:31:17 -0400 [thread overview]
Message-ID: <40D850C5.1080802@nortelnetworks.com> (raw)
In-Reply-To: <1087858881.22687.36.camel@gaston>
Well, I went and opened the case.
Lo and behold the bottom bank had three DIMMs while the top bank had only one.
Not sure if it came like that or if someone messed with it. I moved one of the
DIMMs to even it out, and sure enough its showing up with the full amount now.
Sorry to bother you all...
Chris
next prev parent reply other threads:[~2004-06-22 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 21:11 BUG?: G5 not using all available memory Chris Friesen
2004-06-21 22:01 ` Benjamin Herrenschmidt
2004-06-21 22:32 ` Chris Friesen
2004-06-21 23:01 ` Benjamin Herrenschmidt
2004-06-22 15:01 ` Chris Friesen
2004-06-22 15:31 ` Chris Friesen [this message]
2004-06-23 14:45 ` BUG?: G5 not using all available memory -- SOLVED Timothy Miller
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=40D850C5.1080802@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=benh@kernel.crashing.org \
--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