linux-kernel - Re: Accessing more than 2GB of memory with a 32 bit kernel

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]

Message-ID: <51B8B153.40100@ono.com>
Date:	Wed, 12 Jun 2013 19:35:15 +0200
From:	JA Magallón <jamagallon@....com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Accessing more than 2GB of memory with a 32 bit kernel

On 06/12/2013 06:54 PM, Simon Brown wrote:
> Hello,
>
> For the sake of an old prototype peripheral I'm using a non PAE 32 bit
> x86 kernel and I'm having trouble accessing memory above 2 GB. The
> system has 4GB installed and all is well with a PAE kernel.
>

I have also 3 or 4 32-bit boxes running with more than 2Gb, I will try to
give you some ideas...

> I'm obviously expecting to lose some memory due to memory mapped devices
> but I wasn't expecting to lose 2GB. Instead I'm suspecting a BIOS bug.
> The system reports:
> free -m
>               total       used       free     shared    buffers
>               cached
> Mem:          2012        491       1521          0         40
> 277
>
> The mtrr table looked odd so I enabled sanitisation:
> [    0.000000] original variable MTRRs
> [    0.000000] reg 0, base: 2GB, range: 2GB, type UC
> [    0.000000] reg 1, base: 0GB, range: 4GB, type WB
> [    0.000000] reg 2, base: 4GB, range: 2GB, type WB
> [    0.000000] total RAM covered: 4096M
> [    0.000000] Found optimal setting for mtrr clean up
> [    0.000000]  gran_size: 64K  chunk_size: 64K         num_reg: 2
> lose cover RAM: 0G
> [    0.000000] New variable MTRRs
> [    0.000000] reg 0, base: 0GB, range: 2GB, type WB
> [    0.000000] reg 1, base: 4GB, range: 2GB, type WB
>
> I don't understand the gap in the new table.
>

MTRR is set initially like:
- 4GB at address 0x, from which the last 2GB are unusable = 2GB cacheable
- 2GB more starting at address 4GB, normally cacheable

After the cleanup, the 4-2 part is cleaned and left as just 2:
- 2GB at 0
- a hole from 2GB to 4GB
- 2GB at 4Gb

It looks like your mobo BIOS maps the second GB pair up from address 4GB,
so you can not use them without PAE. If you find an option
in your BIOS to force it to map them under 4GB, the a normal kernel
with CONFIG_HIGHMEM4G=y will see it.
Look in BIOS for something like 'endable/disable continous/discrete mtrr'
or 'harware memory hole' or something like that.

> The motherboard is an Asus P5K with an Intel® P35 chipset. I'm using the
> ubuntu lucid kernel (2.6.32) but the problem is also present with the
> ubuntu precise kernel.
> I'm at the limit of my understanding, can anyone advise how to debug
> further?
>
-- 
J.A. Magallon <jamagallon()ono!com>        \               Winter is coming...
--
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/