Bug 1593878 - 96% of 64GB of RAM reserved, only 2.3 GB available for use
Summary: 96% of 64GB of RAM reserved, only 2.3 GB available for use
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-21 18:24 UTC by Susi Lehtola
Modified: 2018-06-25 22:47 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-25 10:05:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
dmesg output (61.37 KB, text/plain)
2018-06-21 18:36 UTC, Susi Lehtola 		no flags Details
View All

Description Susi Lehtola 2018-06-21 18:24:46 UTC 
This is an issue I've brought up on fedora-list at

https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/FNBHYDDH2HMKQEKKFKN7NSRUFWW74IZS/

The problem is that my HP EliteDesk 800 G3 workstation

[ 0.000000] DMI: HP HP EliteDesk 800 G3 TWR/8298, BIOS P01 Ver. 02.06 06/09/2017 

has 64 GB of RAM installed, but only 2.3 GB is available for use

$ free
              total        used        free      shared  buff/cache   available
Mem:        2400708      684936      399032      160620     1316740     1291144
Swap:      62499836         512    62499324


According to dmesg, it appears that the kernel *does* see all 64 gigs, BUT OVER 60 GB IS RESERVED MEMORY!!

[ 0.000000] Memory: 2326720K/66985176K available (12300K kernel code, 1568K rwdata, 3836K rodata, 2124K init, 1368K bss, 64658456K reserved, 0K cma-reserved) 


When I got the desktop last fall and installed Fedora 27 on it, all 64 GB was available. The hardware configuration hasn't changed in any way since then. I had the issue both in Fedora 27, and now in Fedora 28.
Comment 1 Laura Abbott 2018-06-21 18:33:30 UTC 
Can you share the full dmesg?
Comment 2 Susi Lehtola 2018-06-21 18:36:50 UTC 
Created attachment 1453576 [details]
dmesg output
Comment 3 Susi Lehtola 2018-06-25 10:05:24 UTC 
Turns out this was solved by a BIOS update.
Note You need to log in before you can comment on or make changes to this bug.