From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org, crmotherboard@intel.com
Subject: Re: Case: 7454422: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards. (FULL DMESG)
Date: Thu, 31 May 2007 09:08:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705310906590.6709@p34.internal.lan> (raw)
In-Reply-To: <465EC464.7050302@gmail.com>
On Thu, 31 May 2007, Parag Warudkar wrote:
> Robert Hancock wrote:
>> 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.)
>>
> Yep, and that would be much easier too.
>
> I am curious though as this seems to be somewhat common a problem, could we
> make the kernel analyze which memory is not cacheable (it already knows this
> via MTRR) and not use that portion for anything? Plus may be warn the user to
> contact their BIOS vendor to correct the problem?
>
> I think that would be possible - even if the kernel knows late that the
> memory was uncached we could migrate those pages in that region to someplace
> else?
>
> Parag
>
That is an excellent question and I wonder the same thing. I also had
this problem when I only used 4GB of ram and upgraded the (another
motherboard, I have two) past version 1666P and I had no idea what was
going on other than the BIOS did not work correctly.
In this case however it worked with 4GB with bios version 1612P but not
with 8GB. Is this the case of a buggy BIOS for the 965 chipset or do
Intel boards have a lot of issues?
Justin.
next prev parent reply other threads:[~2007-05-31 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 0:57 Parag Warudkar
2007-05-31 4:38 ` Robert Hancock
2007-05-31 12:33 ` Justin Piszcz
2007-05-31 12:49 ` Parag Warudkar
2007-05-31 13:08 ` Justin Piszcz [this message]
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=Pine.LNX.4.64.0705310906590.6709@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=crmotherboard@intel.com \
--cc=hancockr@shaw.ca \
--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
all inboxes | Powered by JetHome®