linux-kernel - Re: 2.6.27 mtrr fixes do not work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Aug 2008 16:52:21 +0200
From:	Alexander Huemer <alexander.huemer@....ac.at>
To:	Yinghai Lu <yhlu.kernel@...il.com>
CC:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: 2.6.27 mtrr fixes do not work

Yinghai Lu wrote:
> On Thu, Aug 14, 2008 at 7:09 AM, Alexander Huemer
> <alexander.huemer@....ac.at> wrote:
>   
>> Yinghai Lu wrote:
>>     
>>> On Thu, Aug 7, 2008 at 4:30 PM, Alexander Huemer
>>> <alexander.huemer@....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
    mtrr: type mismatch for d8000000,800000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,400000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,200000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,100000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,80000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,40000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,20000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,10000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,8000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,4000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,2000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,1000 old: write-back new:
    write-combining
    mtrr: type mismatch for d8000000,2000000 old: write-back new:
    write-combining
    # grep MemTotal /proc/meminfo                         
    MemTotal:      4041088 kB
    # grep MTRR /usr/src/linux/.config                 
    CONFIG_MTRR=y
    CONFIG_MTRR_SANITIZER=y
    CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
    CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
    # dmesg|grep uvesafb  
    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
    uvesafb: XGI Technology, Inc., Volari Z9s, 1.09.10, OEM: XGI, VBE v3.0
    uvesafb: VBIOS/hardware supports DDC2 transfers
    uvesafb: monitor limits: vf = 97 Hz, hf = 129 kHz, clk = 364 MHz
    uvesafb: scrolling: redraw
    uvesafb: framebuffer at 0xd8000000, mapped to 0xffffc20002100000,
    using 10240k, total 32768k
    # 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
    #


-- 
regards
alex

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