From: Andi Kleen <ak@muc.de>
To: YhLu <YhLu@tyan.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: X86_64 kernel support MAX memory.
Date: 15 Feb 2005 23:42:26 +0100
Date: Tue, 15 Feb 2005 23:42:26 +0100 [thread overview]
Message-ID: <20050215224226.GA87835@muc.de> (raw)
In-Reply-To: <3174569B9743D511922F00A0C943142308085866@TYANWEB>
On Tue, Feb 15, 2005 at 02:34:17PM -0800, YhLu wrote:
> If only use 64G RAM, it works well.
Are you sure the RAM is not broken? The more you have of it
the more likely one DIMM is bad.
Otherwise debug it. What's the oops dump?
-Andi
next prev parent reply other threads:[~2005-02-15 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 22:34 X86_64 kernel support MAX memory YhLu
2005-02-15 22:42 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-15 23:32 YhLu
2005-02-15 22:57 YhLu
2005-02-15 22:55 ` Andi Kleen
2005-02-15 18:49 YhLu
2005-02-15 20:14 ` Andi Kleen
2005-02-15 3:32 YhLu
2005-02-15 12:08 ` Andi Kleen
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=20050215224226.GA87835@muc.de \
--to=ak@muc.de \
--cc=YhLu@tyan.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