[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 Mon, 29 Apr 2019 20:00:59 + ** Changed in: lshw (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777131 Title: Wrong RAM size shown for server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777131] Re: Wrong RAM size shown for server
[VERIFICATION XENIAL] I can't reproduce the problem myself as I don't have such HW at my disposal, but the following have been brought to my attention (from an impacted users): This was tested against the lswh found in xenial-proposed. It is now displaying the right size. .. *-bank:0 description: product: vendor: physical id: 0 serial: slot: => size: 64GiB width: 72 bits clock: 2400MHz (0.4ns) .. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777131 Title: Wrong RAM size shown for server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777131] Re: Wrong RAM size shown for server
Hello Alexander, or anyone else affected, Accepted lshw into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lshw/02.17-1.1ubuntu3.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lshw (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777131 Title: Wrong RAM size shown for server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777131] Re: Wrong RAM size shown for server
I uploaded the package in the Xenial upload queue for SRU verification team approval. Once approved, the package will start building in xenial- proposed, entering the testing phase of the SRU. Eric ** Description changed: [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: product: vendor: physical id: serial: slot: ==> 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 impacter 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.00] Memory: 791161372K/803909324K available (8541K kernel code, 1313K rwdata, 4000K rodata, 1512K init, 1316K bss, 12747952K reserved, 0K cma-reserved) ubuntu:~$ free -m totalusedfree shared buff/cache available Mem: 7726583828 768156 18 672 766751 Swap: 8191 08191 /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) ||/ NameVersion Architecture Description +++-===---= un maas (no description available) ii maas-cli2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS client and command-line interface un maas-cluster-controller (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-dns2.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-controller2.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
[Bug 1777131] Re: Wrong RAM size shown for server
** Description changed: + [IMPACT] + System with DIMM size of >32GB aren't reporting exact size value when using 'lshw'. + Giving wrong information to hardware inventory system which collect data from 'lshw', any hardware certification vendor testing, ... + + [TEST CASE] + + * Use system running Xenial with DIMM of >32GB of RAM + ** sudo lshw -C memory + + Output: + ... + *-bank:0 + + physical id: 0 + serial: + slot: ChannelA-DIMM0 + size: 31GiB + width: 64 bits + + + *-bank:0 + description: + product: + vendor: + physical id: + serial: + slot: + ==> size: 31GiB + ... + ... + + In this case, size should be 64GB, just like 'dmidecode' shows + + + [POTENTIAL REGRESSION] + + [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.00] Memory: 791161372K/803909324K available (8541K kernel code, 1313K rwdata, 4000K rodata, 1512K init, 1316K bss, 12747952K reserved, 0K cma-reserved) ubuntu:~$ free -m totalusedfree shared buff/cache available Mem: 7726583828 768156 18 672 766751 Swap: 8191 08191 /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) ||/ NameVersion Architecture Description +++-===---= un maas (no description available) ii maas-cli2.3.3-6498-ge4db91d-0ubuntu1~16.04.1 all MAAS client and command-line interface un maas-cluster-controller (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-dns2.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-controller2.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 (no description available) un python-django-maas (no description available) un python-maas-client (no description available) un python-maas-provisioningserver (no description available)
[Bug 1777131] Re: Wrong RAM size shown for server
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 ** Bug watch added: Ezix Trac #662 http://ezix.org/project/ticket/662 ** Also affects: lshw (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: lshw (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lshw (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: lshw (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: lshw (Ubuntu Xenial) Status: New => In Progress ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777131 Title: Wrong RAM size shown for server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777131] Re: Wrong RAM size shown for server
** Changed in: lshw (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777131 Title: Wrong RAM size shown for server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777131] Re: Wrong RAM size shown for server
Commissioning with Bionic indeed works fine, gets RAM correctly: https://pastebin.canonical.com/p/G7B7zVMkFF/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777131 Title: Wrong RAM size shown for server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777131] Re: Wrong RAM size shown for server
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lshw (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777131 Title: Wrong RAM size shown for server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777131] Re: Wrong RAM size shown for server
Alexander, >From the looks of the lshw it seems that it reports 12 dimms of ~34GB each. This means that the RAM size is being reported incorrectly by LSHW and, as such, MAAS reflects that information. As such, I'll mark this invalid for MAAS, and open a task for lshw. That said, i noticed you are using 2.3.3, and I'm guessing you are using Xenial for commissioning. Could you please switch to bionic for commissioning and see if the issue persists? A newer version of lshw is in Bionic which may have already fixed this issue. ** Changed in: maas Status: Incomplete => Invalid ** Also affects: lshw (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777131 Title: Wrong RAM size shown for server To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1777131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
