linux-kernel - Which patch fix the 8G memory problem on x64 platform?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <ac8af0be0611270202i54e376b5jedf91fd7cba35434@mail.gmail.com>
Date:	Mon, 27 Nov 2006 02:02:06 -0800
From:	"Zhao Forrest" <forrest.zhao@...il.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	discuss@...-64.org, linux-kernel@...r.kernel.org
Subject: Which patch fix the 8G memory problem on x64 platform?

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/