public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* (no subject)
@ 2011-01-19 22:02 werner
  0 siblings, 0 replies; only message in thread
From: werner @ 2011-01-19 22:02 UTC (permalink / raw)
  To: aarcange, bp, hannes, linux-kernel

Hello

Only for your information, after the crash report, I 
recompiled the kernel with switching off HUGEPAGE, and 
then it runs normally.  This means, that the problem 
really was caused by khugepaged, not by any other change 
from 2.6.37 to 2.6.38-rc1 .  Below I dont give the whole 
configure file, but only that part where is the difference 
(the line marked as comment)

I didnt yet try any patch.

wl


  ...
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
# CONFIG_TRANSPARENT_HUGEPAGE is not set
CONFIG_HIGHPTE=y
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
CONFIG_X86_RESERVE_LOW=64
---
Professional hosting for everyone - http://www.host.ru

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2011-01-19 22:03 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-19 22:02 werner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox