public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards.
Date: Wed, 30 May 2007 08:27:45 -0600	[thread overview]
Message-ID: <465D89E1.7030301@shaw.ca> (raw)
In-Reply-To: <Pine.LNX.4.64.0705300440530.3755@p34.internal.lan>

Justin Piszcz wrote:
> Kernel dmesg attached from 8GB bootup.

It looks like part of the start of the output was truncated..

> Robert, how come the option is not applicable in 64-bit mode? If I want 
> to use all 8GB of memory I need to run a 32-bit kernel?
> 
> Justin.
> 

Highmem and PAE (which are essentially what the 4GB/64GB memory options 
control) are not needed in 64-bit mode, since we can access the entire 
64-bit address space directly.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


  parent reply	other threads:[~2007-05-30 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.4kEpre7NAj1mG6fooUMp/WVc8tg@ifi.uio.no>
2007-05-30  4:08 ` Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards Robert Hancock
2007-05-30  8:43   ` Justin Piszcz
2007-05-30  8:54     ` Justin Piszcz
2007-05-30 14:27     ` Robert Hancock [this message]
2007-05-30 14:33       ` Case: 7454422: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards. (FULL DMESG) Justin Piszcz
2007-05-30 14:36         ` Justin Piszcz
2007-05-30 14:50         ` Case: 7454422: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards Ernst Herzberg
2007-05-29 23:07 Justin Piszcz
2007-05-30 20:49 ` Andi Kleen

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=465D89E1.7030301@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=jpiszcz@lucidpixels.com \
    --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