group.of.nepali.translators team mailing list archive

Thread
Date

[Bug 1039701] Re: Wrong RAM memory size

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1039701@xxxxxxxxxxxxxxxxxx>
Date: Wed, 08 Jun 2016 22:59:53 -0000
Reply-to: Bug 1039701 <1039701@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug was fixed in the package lshw - 02.17-1.1ubuntu3.1

---------------
lshw (02.17-1.1ubuntu3.1) xenial; urgency=medium

  * Use upstream solution for avoiding /dev/mem accesses on !x86,
    fixing a memory size detection regression (LP: #1039701):
     - Drop: smbios-noscan.patch
     - Add: use-sysfs-for-DMI-info-when-available-696-666-664.patch

 -- dann frazier <dann.frazier@xxxxxxxxxxxxx>  Wed, 01 Jun 2016 15:46:02
-0600

** 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/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 Released

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