[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440808291043s774d3913k85de758f2e23b24b@mail.gmail.com>
Date: Fri, 29 Aug 2008 10:43:43 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Alexander Huemer" <alexander.huemer@....ac.at>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Helge Hafting" <helge.hafting@...el.hist.no>
Subject: Re: 2.6.27 mtrr fixes do not work
On Fri, Aug 29, 2008 at 8:09 AM, Alexander Huemer
<alexander.huemer@....ac.at> wrote:
> Yinghai Lu wrote:
>> On Mon, Aug 25, 2008 at 4:29 PM, Alexander Huemer
>> <alexander.huemer@....ac.at> wrote:
>>> Yinghai Lu wrote:
>>>> On Mon, Aug 25, 2008 at 1:44 PM, Yinghai Lu <yhlu.kernel@...il.com> wrote:
>>>>
>>>>> On Mon, Aug 25, 2008 at 1:24 PM, Alexander Huemer
>>>>> <alexander.huemer@....ac.at> wrote:
>>>>>
>>>>>
>>>>>> what do you mean with tip/master?
>>>>>>
>>>>> http://people.redhat.com/mingo/tip.git/readme.txt
>>>>>
>>>>>
>>>>>> here is my .config: http://xx.vu/~ahuemer/config.txt
>>>>>>
>>>> using your config, i do get mtrr cleanup
>>>>
>>> very interesting, thx.
>>> so, what can i do to make it working here?
>>> are there some more debug options i could turn on?
>>>
>>
>> can you post whole boot log with command line
>>
>> console=uart8250,io,0x3f8,115200n8 debug show_msr=1
>>
>> assume you have serial console...
>>
>> YH
> yinghai,
>
> there are quite good news! 2.6.27-rc5 brought some significant changes.
> now i get this:
>
> # dmesg|grep -E "(mtrr|uvesafb)"
> Command line: root=/dev/sda1 video=uvesafb:1280x1024p-97,mtrr:2
> debug show_msr=1
> mtrr: your BIOS has set up an incorrect mask, fixing it up.
> Kernel command line: root=/dev/sda1
> video=uvesafb:1280x1024p-97,mtrr:2 debug show_msr=1
> 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
> mtrr: 0xd8000000,0x2000000 overlaps existing 0xd8000000,0x800000
> # grep -E "(^\(WW\)|^\(EE\)|^\(NI\)|^\(??\))" /var/log/Xorg.0.log
> (WW) VESA(0): Failed to set up write-combining range
> (0xd8000000,0x2000000)
> # cat /proc/mtrr
> reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> reg02: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
> reg03: base=0xd8000000 (3456MB), size= 8MB: write-back, count=1
it seems BIOS setup extra entry (8M) and that is conflict with that of
from graphical card.
can you send out
dmesg -s 262144 > dmesg.txt
and
lspci -vvxxx
lspci -tv
so could find out if your graphical card is really allocated the memory area...
YH
--
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/
Powered by blists - more mailing lists