group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #30148
[Bug 1777131] Re: Wrong RAM size shown for server
This bug was fixed in the package lshw - 02.17-1.1ubuntu3.6
---------------
lshw (02.17-1.1ubuntu3.6) xenial; urgency=medium
* d/p/lshw-reports-wrong-memory-size.patch:
- Implement DMI memory reporting when DIMM
size is >32GiB (LP: #1777131)
-- Eric Desrochers <eric.desrochers@xxxxxxxxxxxxx> Mon, 29 Apr 2019
20:00:59 +0000
** Changed in: lshw (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1777131
Title:
Wrong RAM size shown for server
Status in MAAS:
Invalid
Status in lshw package in Ubuntu:
Fix Released
Status in lshw source package in Xenial:
Fix Released
Bug description:
[IMPACT]
System with DIMM size of >32GB aren't reporting exact size value when using 'lshw'.
Giving wrong information to hardware inventory system which may
collect data from 'lshw', any hardware certification vendor testing,
wrong RAM amount shown in the MAAS UI, ...
[TEST CASE]
* Use system running Xenial with DIMM >32GB of RAM
** sudo lshw -C memory
Output:
...
*-bank:0
description: <REDACTED>
product: <REDACTED>
vendor: <REDACTED>
physical id: <REDACTED>
serial: <REDACTED>
slot: <REDACTED>
==> size: 31GiB
...
...
In this case, size should be 64GB, just like 'dmidecode' shows
[POTENTIAL REGRESSION]
Very low, the fix only take care of DIMM size handling to support DIMM
gt 32GB.
A test package has been provided to an impacted user, here's what has
been brought to my attention:
"
That seems to be working. Dumped a copy of the lshw output to two files, "before" and "after".
$ diff before after
38c38
< size: 31GiB
---
> size: 64GiB
and so on down the line for each memory chip.
"
[OTHER INFORMATIONS]
Upstream bug:
https://ezix.org/project/ticket/662
Upstream commit:
https://ezix.org/src/pkg/lshw/commit/640615983fbf976e66931164a9ae1bd64da9668b
I'm working on a backport fix for Xenial.
# git describe --contains 6406159
B.02.17~26
# rmadison
=> lshw | 02.17-1.1ubuntu3.5 | xenial-updates
lshw | 02.18-0.1ubuntu6 | bionic
lshw | 02.18-0.1ubuntu6.18.04.1 | bionic-updates
lshw | 02.18-0.1ubuntu7 | cosmic
lshw | 02.18-0.1ubuntu7 | disco
lshw | 02.18.85-0.1ubuntu1 | eoan
[ORIGINAL DESCRIPTION]
Currently MAAS relies on DMI for the info about RAM size.
DMI seems not to be always correct, this results in wrong RAM amount shown in the MAAS UI.
In my case :
......
handle: DMI:0017
- lshw:description:
DIMM Synchronous 2666 MHz (0.4 ns)
- lshw:product:
M386A8K40BM2-CTD
- lshw:vendor:
Samsung
- lshw:physid:
0
- lshw:serial:
375610DE
- lshw:slot:
P1-DIMMA1
- lshw:size:
units: bytes
34358689792
......
full machine yaml : https://pastebin.canonical.com/p/TqpvzXj2sx/
However product M386A8K40BM2-CTD is actually 64GB:
https://memory.net/product/m386a8k40bm2-ctd-samsung-1x-64gb-ddr4-2666-lrdimm-pc4-21300v-l-quad-rank-x4-module/
I have 12 of those, and on boot it shows me the correct amount 12 *
64GB:
ubuntu:~$ dmesg | grep Memory
[ 0.000000] Memory: 791161372K/803909324K available (8541K kernel code, 1313K rwdata, 4000K rodata, 1512K init, 1316K bss, 12747952K reserved, 0K cma-reserved)
ubuntu:~$ free -m
total used free shared buff/cache available
Mem: 772658 3828 768156 18 672 766751
Swap: 8191 0 8191
----------------------------------------------------------------
/var/log/maas : https://private-
fileshare.canonical.com/~dima/varlogmaas-15062018.tar
ubuntu$ 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
+++-===============================-====================================-============-=============================================
un maas <none> <none> (no description available)
ii maas-cli 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.3.3-6498-ge4db91d-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.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions
