mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: mrustad@mac.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16 hugetlbfs problem - DEBUG_PAGEALLOC
Date: Fri, 24 Mar 2006 18:53:31 -0800	[thread overview]
Message-ID: <20060324185331.56837b0a.akpm@osdl.org> (raw)
In-Reply-To: <200603250124.k2P1OKg21526@unix-os.sc.intel.com>

"Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
>
> Mark Rustad wrote on Friday, March 24, 2006 9:52 AM
>  > I have narrowed this down to DEBUG_PAGEALLOC. If that option is  
>  > enabled, attempts to reference areas mmap-ed from hugetlbfs files  
>  > fault forever. You can see that I had that set in the failing config  
>  > I reported below.
> 
>  Yeah, it turns out that the debug option is not compatible with hugetlb
>  page support. That debug option turns off PSE. Once it is turned off in
>  CR4, cpu will ignore pse bit in the pmd and causing infinite page-not-
>  present fault :-(

I wonder if any of the other architectures which implement both these
features might have problems too.


  parent reply	other threads:[~2006-03-25  2:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 22:10 2.6.16 hugetlbfs problem Mark Rustad
2006-03-22 22:13 ` David S. Miller
2006-03-22 23:32   ` Mark Rustad
2006-03-23  5:43     ` Chen, Kenneth W
2006-03-23 15:36       ` Mark Rustad
2006-03-23 19:13         ` Mark Rustad
2006-03-24 17:52           ` 2.6.16 hugetlbfs problem - DEBUG_PAGEALLOC Mark Rustad
2006-03-25  1:24             ` Chen, Kenneth W
2006-03-25  1:47               ` David S. Miller
2006-03-25  2:53               ` Andrew Morton [this message]
2006-03-25  7:29                 ` Chen, Kenneth W
2006-03-25  8:15                   ` Andrew Morton

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=20060324185331.56837b0a.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrustad@mac.com \
    /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

Powered by JetHome