mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: "Lukas Hejtmanek" <xhejtman@ics.muni.cz>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mtrr madness
Date: Mon, 1 Sep 2008 10:25:33 -0700	[thread overview]
Message-ID: <86802c440809011025ue34800w179ee03d2cf214d1@mail.gmail.com> (raw)
In-Reply-To: <48BC2405.9070403@shaw.ca>

On Mon, Sep 1, 2008 at 10:19 AM, Robert Hancock <hancockr@shaw.ca> wrote:
> Lukas Hejtmanek wrote:
>>
>> Hello,
>>
>> it seems that all linux kernels contain a bug with mtrr:
>>
>>  cat /proc/mtrr reg00: base=0x00000000 (   0MB), size=198656MB:
>> write-back, count=1
>> reg01: base=0x80000000 (2048MB), size=197120MB: write-back, count=1
>> reg02: base=0x9fc00000 (2556MB), size=196612MB: uncachable, count=1
>> reg03: base=0x100000000 (4096MB), size=200704MB: write-back, count=1
>> reg04: base=0x200000000 (8192MB), size=204800MB: write-back, count=1
>>
>> (watch the size)
>>
>> it is definitely  present in the kernels 2.6.16, 2.6.24, 2.6.25, 2.6.26.
>>
>> 198656 is 0x3080000000, the correct value would be 0x80000000, similarly
>> 197120 is 0x3020000000, the correct would be 0x20000000.
>
> Those are set up by the BIOS, so it would be what's at fault. I think we may
> be adding something to fix this up though?

the fix is in mainline already...,
Author: Yinghai Lu <yhlu.kernel@gmail.com>
Date:   Thu Aug 21 20:24:24 2008 -0700

    x86: work around MTRR mask setting

please try 2.6.27-rc5...

YH

  reply	other threads:[~2008-09-01 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.oAfJTOqZ/UBF74k5hFotOE73/z4@ifi.uio.no>
2008-09-01 17:19 ` Robert Hancock
2008-09-01 17:25   ` Yinghai Lu [this message]
2008-09-01 14:25 Lukas Hejtmanek

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=86802c440809011025ue34800w179ee03d2cf214d1@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xhejtman@ics.muni.cz \
    /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®