DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=YSM1UC/rhhHXZnBGNRM6IKsvzYeNb6cZAm4Gxvn/N6ZPIL0avgRJcR6D9pi+kiRufTZTzkRoP4PxAx12nK4LvUrOnk7fV/VcGFA6AMcXm72i/RlBIqz8WGea5fSXHZ82z9MTj34c5rhzdUqI3uPOJP6/6C6RTn4wD5CawTRCAe8=
Message-ID: <ac8af0be0611270202i54e376b5jedf91fd7cba35434@mail.gmail.com>
Date: Mon, 27 Nov 2006 02:02:06 -0800
From: "Zhao Forrest" <forrest.zhao@gmail.com>
To: "Andi Kleen" <ak@suse.de>
Subject: Which patch fix the 8G memory problem on x64 platform?
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 800
Lines: 21

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.

This bug also happens with latest sles10 kernel(2.6.16.21-0.25-smp),
which is based on 2.6.16.21.

Do you know what patch fixed this bug between  2.6.16.32 and 2.6.18.3?
Then we could backport the patch to both 2.6.16.32 and sles10 kernel.

Thanks,
Forrest
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/