Re: 2.6.27 mtrr fixes do not work

["Yinghai Lu" <yhlu.kernel@gmail.com>]

On Thu, Aug 21, 2008 at 7:52 AM, Alexander Huemer
<alexander.huemer@sbg.ac.at> wrote:
> Yinghai Lu wrote:
>>
>> On Thu, Aug 14, 2008 at 7:09 AM, Alexander Huemer
>> <alexander.huemer@sbg.ac.at> wrote:
>>
>>>
>>> Yinghai Lu wrote:
>>>
>>>>
>>>> On Thu, Aug 7, 2008 at 4:30 PM, Alexander Huemer
>>>> <alexander.huemer@sbg.ac.at> wrote:
>>>>
>>>>
>>>>>
>>>>> Yinghai Lu wrote:
>>>>>
>>>>>
>>>>
>>>>
>>>>>>>
>>>>>>> can you put "debug" in command line too?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> without mtrr_chunk_size etc in command line...please
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> http://xx.vu/~ahuemer/dmesg_3.txt
>>>>>
>>>>>
>>>>>
>>>>
>>>> do you have
>>>> CONFIG_MTRR=y
>>>> CONFIG_MTRR_SANITIZER=y
>>>> CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
>>>> CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
>>>>
>>>> in your .config?
>>>>
>>>> YH
>>>>
>>>>
>>>
>>> 2.6.27_rc3 does not solve the problem either.
>>> what can i do to help?
>>>
>>
>> please send out you config
>>
>> YH
>>
>
> yinghai,
>
> i just tried out 2.6.27-rc4, unfortunately without success.
>
> here are my settings again,
> if you need more info, just tell me.
>
> as you can see, the mtrr size values are complete nonsense.
> the framebuffer should be at d8000000.
> i am unsure if this is the fault of the kernel or the bios.
> or should the MTRR_SANITIZER resolv all broken bios issues?
>
>   # uname -a
>   Linux seaburg 2.6.27-rc4-blackbit #1 SMP Thu Aug 21 15:53:38 CEST
>   2008 x86_64 Intel(R) Xeon(R) CPU E5420 @ 2.50GHz GenuineIntel GNU/Linux
>   # grep -E "(^\(WW\)|^\(EE\)|^\(NI\)|^\(??\))" /var/log/Xorg.0.log
>   (WW) VESA(0): Failed to set up write-combining range
>   (0xd8000000,0x2000000)
>   # dmesg|grep mtrr                                                 Command
> line: root=/dev/sda1
>   video=uvesafb:1280x1024-24@97,mtrr:3,ywrap mtrr_chunk_size=512m
>   Kernel command line: root=/dev/sda1
>   video=uvesafb:1280x1024-24@97,mtrr:3,ywrap mtrr_chunk_size=512m

please boot without mtrr_chunk_size=512m
and put debug in your command line


>   # cat /proc/mtrr
>   reg00: base=0x00000000 (   0MB), size=198656MB: write-back, count=1
>   reg01: base=0x80000000 (2048MB), size=197632MB: write-back, count=1
>   reg02: base=0x100000000 (4096MB), size=197632MB: write-back, count=1

another case of crazy size in /proc/mtrr

it is E5420, maybe mtrr code has problem to handle that cpu?

YH