public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "werner" <w.landgraf@ru.ru>
To: aarcange@redhat.com, bp@amd64.org, hannes@cmpxchg.org,
	linux-kernel@vger.kernel.org
Subject: 
Date: Wed, 19 Jan 2011 18:02:56 -0400	[thread overview]
Message-ID: <web-442704529@zbackend1.aha.ru> (raw)

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

                 reply	other threads:[~2011-01-19 22:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=web-442704529@zbackend1.aha.ru \
    --to=w.landgraf@ru.ru \
    --cc=aarcange@redhat.com \
    --cc=bp@amd64.org \
    --cc=hannes@cmpxchg.org \
    --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