mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
Date: Fri, 1 Jun 2007 15:19:12 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706011519080.6696@p34.internal.lan> (raw)
In-Reply-To: <200706011210.15808.jbarnes@virtuousgeek.org>

It works ok on
my machine (correctly detects the condition, adjusts end_pfn, and keeps
the machine fast), aside from the fact that X won't start.

But X won't start? :\

On Fri, 1 Jun 2007, Jesse Barnes wrote:

>> and the MTRRs (from /proc/mtrr, from private email):
>>
>> reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
>> reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
>> reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
>> reg03: base=0xcf800000 (3320MB), size=   8MB: uncachable, count=1
>> reg04: base=0xcf700000 (3319MB), size=   1MB: uncachable, count=1
>> reg05: base=0x100000000 (4096MB), size=4096MB: write-back, count=1
>> reg06: base=0x200000000 (8192MB), size= 512MB: write-back, count=1
>> reg07: base=0x220000000 (8704MB), size= 128MB: write-back, count=1
>>
>> so the ranges mapped as cacheable are:
>>
>> 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.
>
> If it's just 64M you'll end up losing, you could try the "[RFC] trim memory
> not covered by MTRR WB type" patch I posted yesterday.  It won't reinit the
> MTRRs (maybe we should) but it will at least prevent your system from
> crawling if the BIOS doesn't set them up right.  That would at least let you
> use most of your memory until the BIOS guys acknowledge that they have a
> problem (or we get proper PAT support, which I think would make this problem
> go away as well).
>
> Jesse
>

  parent reply	other threads:[~2007-06-01 19:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 18:14 Justin Piszcz
2007-06-01 19:10 ` Jesse Barnes
2007-06-01 19:17   ` Justin Piszcz
2007-06-01 19:19   ` Justin Piszcz [this message]
2007-06-01 19:21     ` Jesse Barnes
2007-06-01 21:14   ` Andi Kleen
2007-06-01 20:19     ` Justin Piszcz
2007-06-01 20:24       ` Andi Kleen
2007-06-01 20:26         ` Justin Piszcz
2007-06-01 21:07     ` Jesse Barnes
2007-06-01 21:19       ` Andi Kleen
2007-06-01 21:35         ` Jesse Barnes
2007-06-01 21:41         ` Jesse Barnes
2007-06-02  1:05           ` Venki Pallipadi
2007-06-02  1:15             ` Jesse Barnes
2007-06-02  8:43               ` Justin Piszcz
2007-06-02  9:22             ` Andi Kleen
2007-06-02 20:11               ` Justin Piszcz
2007-06-03  9:15                 ` Matt Keenan
2007-06-04 15:40                   ` Jesse Barnes
2007-06-04 15:48                     ` Ray Lee
2007-06-04 15:49                       ` Justin Piszcz
2007-06-04 16:01                         ` Ray Lee
2007-06-04 15:54                       ` Jesse Barnes
2007-06-04 18:24                       ` Andi Kleen
2007-06-04 18:13           ` Eric W. Biederman
2007-06-04 18:22             ` Justin Piszcz
2007-06-04 19:08               ` Justin Piszcz
2007-06-04 19:17               ` Jesse Barnes
2007-06-04 19:18               ` Alan Cox
2007-06-04 21:01                 ` Eric W. Biederman
2007-06-05  0:59                   ` Yinghai Lu
2007-06-05  1:38                     ` Eric W. Biederman
2007-06-05  9:46                       ` Andi Kleen
2007-06-05 13:18                         ` Justin Piszcz
2007-06-05 17:20                         ` Jesse Barnes
2007-06-07  8:47                     ` Andi Kleen
2007-06-04 19:23               ` Andi Kleen
2007-06-04 19:24                 ` Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? II Andi Kleen
2007-06-05  0:54                 ` Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? Yinghai Lu

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.0706011519080.6696@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=jbarnes@virtuousgeek.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

all inboxes | Powered by JetHome®