Re: Strange mtrrs in Aspire One

[Yinghai Lu]

On Sat, Oct 4, 2008 at 10:55 AM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> On Sat, Oct 4, 2008 at 6:22 AM, J.A. Magallón <jamagallon@xxxxxxx> wrote:
>> On Mon, 29 Sep 2008 18:05:51 -0700, "Yinghai Lu" <yinghai@xxxxxxxxxx> wrote:
>>
>>> On Mon, Sep 29, 2008 at 4:57 PM, J.A. Magallón <jamagallon@xxxxxxx> wrote:
>>> > Hi all...
>>> >
>>> > My aspire one is giving some strange MTRR settings with rc7-git5 (and
>>> > prevous kernels, but that is what I run now...):
>>> >
>>> > one:~> cat /proc/mtrr
>>> > reg00: base=0xfffe0000 (4095MB), size= 128KB: write-protect, count=1
>>> > reg01: base=0xfffc0000 (4095MB), size= 128KB: uncachable, count=1
>>>
>>> could make mtrr_cleanup to support 128K gran_size
>>>
>>> > reg02: base=0x00000000 (   0MB), size= 256MB: write-back, count=1
>>> > reg03: base=0x10000000 ( 256MB), size= 256MB: write-back, count=1
>>> > reg04: base=0x1f800000 ( 504MB), size=   8MB: uncachable, count=1
>>> > reg05: base=0x1f600000 ( 502MB), size=   2MB: uncachable, count=1
>>> > reg06: base=0x1f500000 ( 501MB), size=   1MB: uncachable, count=1
>>>
>>> > reg07: base=0x00000000 (   0MB), size= 128KB: uncachable, count=1
>>> ..
>>> >  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>>>
>>> last entry is really sick...
>>>
>>
>> I have applied the patches you have posted in other threads, and this
>> give a very strange result. The mtrr cleanup did nothing, and I had to put
>> some printk's all around.
>
> will have one patch to assume the [0, 1M) to be coverred by var mtrrs.
>

please check other three patches.

[PATCH 1/3] x86: mtrr_cleanup: print out correct type
[PATCH 2/3] x86: mtrr_cleanup: first 1M should be coverred in var mtrrs
[PATCH 3/3] x86: mtrr_cleanup: treat WRPROT as UNCACHEABLE

you may need to boot with "mtrr_gran_size=64k mtrr_chunk_size=64k"

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/