[Bug 1039701] Re: Wrong RAM memory size

[Brian Murray]

Hello Dimitrios, 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.1 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lshw (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lshw in Ubuntu.
https://bugs.launchpad.net/bugs/1039701

Title:
  Wrong RAM memory size

Status in lshw:
  New
Status in MAAS:
  New
Status in landscape-client package in Ubuntu:
  Invalid
Status in lshw package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  Confirmed
Status in lshw source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  lshw is not using smbios to obtain hardware information. This is causing lshw to report incorrect information to user. For example I have a machine which has one physical CPU with 8 cores and 32G of RAM. lshw is reporting the machine has only one physical CPU with 0 cores and 32162MiB of RAM.

  [Test case]
  Run lshw and compare its reported values with what you know the physical system has. To help simplify testing I use this script http://paste.ubuntu.com/16900290/ which can be run with the command `sudo lshw -xml | ./parse_lshw`

  [Regression Potential]
  smbios-noscan.patch was introduced to prevent ARM systems from locking up when lshw is being run. We are replacing this patch with cherry picked commit(8237f8ebb92ebf684c0e6715cc6c28a3b2bb93b8) from https://ezix.org/src/pkg/lshw which was released with lshw-B.02.18. Potentially this could bring back https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 however upstream considers it fixed with the previously mentioned cherry pick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lshw/+bug/1039701/+subscriptions