From: Andi Kleen <ak@suse.de>
To: "Zhao Forrest" <forrest.zhao@gmail.com>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: Which patch fix the 8G memory problem on x64 platform?
Date: Mon, 27 Nov 2006 11:15:55 +0100 [thread overview]
Message-ID: <200611271115.55899.ak@suse.de> (raw)
In-Reply-To: <ac8af0be0611270202i54e376b5jedf91fd7cba35434@mail.gmail.com>
On Monday 27 November 2006 11:02, Zhao Forrest wrote:
> Hi Andi,
>
> The kernel 2.6.18.3 runs very well on my x64 server with 2 CPU's and
> 8G memory; however kernel 2.6.16.32 kernel panic(Kernel panic - not
> syncing: Attempted to kill init) under the stress test. After I use
> mem=4000M for kernel 2.6.16.32, the kernel panic doesn't happen under
> stress test.
I'm not aware of a "8G memory problem"
Best you write a full bug report and possibly git bisect it.
-Andi
next prev parent reply other threads:[~2006-11-27 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 10:02 Which patch fix the 8G memory problem on x64 platform? Zhao Forrest
2006-11-27 10:15 ` Andi Kleen [this message]
2006-11-28 5:33 ` Zhao Forrest
2006-11-28 9:45 ` 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=200611271115.55899.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=forrest.zhao@gmail.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