All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wojciech Kromer <wojciech.kromer@dgt.com.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: Intel-Quad on GA-P35-S3 motherboard with 4*2GB
Date: Tue, 18 Sep 2007 16:35:43 +0200	[thread overview]
Message-ID: <46EFE23F.8090100@dgt.com.pl> (raw)
In-Reply-To: <20070918142047.GF5386@csclub.uwaterloo.ca>


>> [root@kromblack ~]# cat /proc/mtrr
>> reg00: base=0x100000000 (4096MB), size=8192MB: write-back, count=1
>> reg01: base=0x280000000 (10240MB), size=2048MB: uncachable, count=1
>> reg02: base=0x260000000 (9728MB), size= 512MB: uncachable, count=1
>> reg03: base=0x00000000 (   0MB), size=4096MB: write-back, count=1
>> reg04: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1
>> reg05: base=0xa0000000 (2560MB), size= 512MB: uncachable, count=1
>> reg06: base=0x9ff00000 (2559MB), size=   1MB: write-through, count=1
>>     
>
>   
Yes, it's a bit strange, but there should be a way to configure it in linux.
I found only memmap option which does selection of regions, but not 
remapping.
> So first it says there is 8GB ram at 4GB.  Then it deletes the top 2GB
> of that and then another 512MB.  So now there is 5.5GB at 4GB.  It then
> says there is 4GB at 0GB, then deletes the top 1GB of that, and then
> another 512MB, leaving 2.5GB at 0GB.  So overall that sounds like 8GB
> total.  It also seems that if it had mapped 2GB at 0GB and 6GB at 4GB
> the MTRR would have been a heck of a lot simpler (but a 32bit OS would
> have had 512MB less ram of course).
>
>   
I have 64 bit compilation of course.
>> [root@kromblack ~]# dmesg|grep mtrr
>> mtrr: your CPUs had inconsistent variable MTRR settings
>> mtrr: probably your BIOS does not setup all CPUs.
>> mtrr: corrected configuration.
>>     
>
> Now that does sound odd.  How many CPUs does the machine have?
>
>   
It's Intel-quad, so there are 4 CPUs.
> So what does the dmesg say about the memory table it got from the bios?
> That is the e820 table.
>   

It's in prevoius mail:

# dmesg|grep BIOS-e820
> BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
> BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000009fee0000 (usable)
> BIOS-e820: 000000009fee0000 - 000000009fee3000 (ACPI NVS)
> BIOS-e820: 000000009fee3000 - 000000009fef0000 (ACPI data)
> BIOS-e820: 000000009fef0000 - 000000009ff00000 (reserved)
> BIOS-e820: 00000000c0000000 - 00000000c4000000 (reserved)
> BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> BIOS-e820: 0000000100000000 - 0000000260000000 (usable)






  reply	other threads:[~2007-09-18 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14  8:50 Intel-Quad on GA-P35-S3 motherboard with 4*2GB Wojciech Kromer
2007-09-14 13:18 ` Lennart Sorensen
2007-09-18  7:01   ` Wojciech Kromer
2007-09-18 14:20     ` Lennart Sorensen
2007-09-18 14:35       ` Wojciech Kromer [this message]
2007-09-18 14:50         ` Lennart Sorensen
2007-09-19  9:28           ` Wojciech Kromer
2007-09-20  7:43             ` Wojciech Kromer
2007-09-21 15:38               ` Lennart Sorensen
2007-09-21 15:38             ` Lennart Sorensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46EFE23F.8090100@dgt.com.pl \
    --to=wojciech.kromer@dgt.com.pl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.