From: Robert Hancock <hancockr@shaw.ca>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: jpiszcz@lucidpixels.com, linux-kernel@vger.kernel.org
Subject: Re: Case: 7454422: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards. (FULL DMESG)
Date: Wed, 30 May 2007 22:38:22 -0600 [thread overview]
Message-ID: <465E513E.60903@shaw.ca> (raw)
In-Reply-To: <82e4877d0705301757v580a4ca5yebe2a565f0b97552@mail.gmail.com>
Parag Warudkar wrote:
> Robert Hancock wrote:
>
>
>> 0-3319MB
>> 4096-8832MB
>>
>> leaving 64MB of memory at the top of RAM uncached. What do you want to
>> bet that something important (kernel code?) is getting loaded there..
>>
>> So essentially it's a BIOS problem, it's not setting up the MTRRs
>> properly in order to map all of RAM as cacheable. As Andi says, complain
>> to Intel.
>>
>
> Could the BADRAM patch be useful for him?
> http://rick.vanrein.org/linux/badram/download.html has 2.6.21 version.
> It says it supports x86_64. May be using this patch he can exclude
> that RAM from being used/accessed?
I think that mem=8832M would work as well, to make the kernel use only
the memory that is marked cacheable. (It looks like this parameter takes
the highest memory address we want the kernel to use, not the highest
memory amount.)
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-05-31 4:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 0:57 Case: 7454422: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards. (FULL DMESG) Parag Warudkar
2007-05-31 4:38 ` Robert Hancock [this message]
2007-05-31 12:33 ` Justin Piszcz
2007-05-31 12:49 ` Parag Warudkar
2007-05-31 13:08 ` Justin Piszcz
2007-05-31 14:27 ` Robert Hancock
2007-05-31 18:44 ` Justin Piszcz
2007-06-01 16:33 ` Justin Piszcz
2007-06-01 17:57 ` Justin Piszcz
2007-06-01 18:10 ` Justin Piszcz
2007-06-01 20:56 ` Robert Hancock
[not found] <fa.t8TZNHj4vrYcIs37jScT0oZl02s@ifi.uio.no>
[not found] ` <fa.nsJ3dX+uNBCD7bTYffkYm0DLnR4@ifi.uio.no>
[not found] ` <fa.lfTXDj3RBbaCLDUJJFzLVowMlxc@ifi.uio.no>
[not found] ` <fa.lrZMTvBB9xwYW1mcA0nyYFjB9qY@ifi.uio.no>
[not found] ` <fa.AIUKY82rbgpQ/AiIxhRL0fahxaQ@ifi.uio.no>
[not found] ` <fa.yz+v/A2zkJKIswF0Y4Mo4FxwnCI@ifi.uio.no>
2007-05-30 23:29 ` Robert Hancock
2007-05-31 4:56 ` Yinghai Lu
[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 14:27 ` Robert Hancock
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
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=465E513E.60903@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.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