Cavium ThunderX system with 128GigB of memory is reported as having 125.9GigB of memory

[Larry Michel]

I have commissioned some ThunderX systems and maas is reporting 125.9GiB of memory for them instead of 128 GigB.

Machine summary
CPU 48 cores RAM 125.9GiB Storage 4500.9GB over 2 disks

From lshw output:

<lshw:node id="memory" claimed="true" class="memory" handle="">
<lshw:description>System memory</lshw:description>
<lshw:physid>3f</lshw:physid>
<lshw:size units="bytes">135155974144</lshw:size>
</lshw:node>

ubuntu@maas2-production:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-==============================-============-=================================================
ii maas 2.1.0+bzr5480-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.1.0+bzr5480-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.1.0+bzr5480-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.1.0+bzr5480-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.1.0+bzr5480-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.1.0+bzr5480-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.1.0+bzr5480-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.1.0+bzr5480-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.1.0+bzr5480-0ubuntu1~16.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.1.0+bzr5480-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.1.0+bzr5480-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.1.0+bzr5480-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

[Brendan Donegan (brendan-donegan)]

https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8&client=ubuntu#q=135155974144+bytes+to+GiB

MAAS is just going by what lshw sees

[Blake Rouse (blake-rouse)]

I think we might pull from /proc/meminfo now. So if you would provide the output of all commissioning scripts that would be great. They are on the machine details page at the bottom.

Also just note that even though the system has 128GB of memory 125GB might only be usable as the many address ranges are map through the CPU for DMA and other devices.

[Lee Trager (ltrager)]

I don't think /proc/meminfo would be any better. The kernel only shows how much memory is available to the user. For example my laptop has 16GB of RAM however awk '/MemTotal/ { print $2 }' /proc/meminfo shows 16306592 which is 15.5GB. Please do attach it so we can take a look anyway.

Previously we had a bug with some Debian patches applied to lshw that caused something similar. Could you try building and running lshw from source and posting the results?

git clone https://ezix.org/src/pkg/lshw.git
cd lshw
make
sudo ./src/lshw -xml > git_lshw.xml

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]

[Larry Michel (lmic)]

Attached are the requested files.

For lshw from source:

     *-memory
          description: System Memory
          physical id: 33
          slot: System board or motherboard
          size: 128GiB
          capacity: 1TiB

For system lshw:

     *-memory
          description: System memory
          physical id: 3f
          size: 125GiB

?field.comment=Attached are the requested files.

For lshw from source:

     *-memory
          description: System Memory
          physical id: 33
          slot: System board or motherboard
          size: 128GiB
          capacity: 1TiB

For system lshw:

     *-memory
          description: System memory
          physical id: 3f
          size: 125GiB

[Andres Rodriguez (andreserl)]

@Larry,

I dont understand what "For lshw from source" vs "For system lshw" mean?

[Larry Michel (lmic)]

@Andres,

"System lshw" is the lshw that was installed on the system and "lshw from source" is the one built from the git src as Lee requested in comment #4:

git clone https://ezix.org/src/pkg/lshw.git
cd lshw
make
sudo ./src/lshw -xml > git_lshw.xml

[Larry Michel (lmic)]

@ltrager, oops I forgot to include the -xml flag so what's in the attachment is output of "sudo ./src/lshw". I'll re-run.

[Andres Rodriguez (andreserl)]

Right, so this is a bug in LSHW and NOT in MAAS.