lkml.org 
[lkml]   [2008]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] x86_32: trim memory by updating e820 v3
Yinghai Lu wrote:
>> reg00: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1
>> reg01: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1
>> reg02: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
>> reg03: base=0xbf700000 (3063MB), size= 1MB: uncachable, count=1
>> reg04: base=0xbf800000 (3064MB), size= 8MB: uncachable, count=1
>>
>> which screws up the X server's attempt to map the video memory at
>> 0xd0000000.
>
> the BIOS should have set memhole to 2048MB or 2560M instead of 1033MB
>
> good mtrr should
>
>> reg00: base=0x00000000 (0MB), size=2048MB: write-back, count=1
>> reg01: base=0x100000000 (4096MB), size=2048MB: write-back, count=1
>
> or
>
>> reg00: base=0x00000000 (0MB), size=2048MB: write-back, count=1
>> reg01: base=0x80000000 (2048MB), size=512MB: write-back, count=1
>> reg02: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
>> reg03: base=0x140000000 (4096MB), size=512MB: write-back, count=1
>
> so please talk to your HW esp CPU vendor to fix the BIOS problem.

This is a Core 2 Duo CPU, so my CPU vendor is Intel. I assume that the
relevant people are already reading this, no?

I'm not sure what I'm supposed to do? Write an Email to Intel support,
referencing this thread? Doesn't anyone here already know the right
people at Intel who could actually do something about this. I think that
would be more useful since I doubt an email to Intel support would reach
those people...

Regards,
Mika



\
 
 \ /
  Last update: 2008-04-27 10:31    [W:0.178 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site