group.of.nepali.translators team mailing list archive

[dann frazier <dann.frazier@xxxxxxxxxxxxx>]

I've tested the proposed fix on two different ARM systems (APM Mustang
and Cavium ThunderX). The output is identical, and there is no system
crash. strace shows that no attempt is made to open /dev/mem, which was
the original issue in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=740034.

** Also affects: lshw (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: landscape-client (Ubuntu Xenial)
   Importance: Undecided
       Status: New

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

** Changed in: lshw (Ubuntu Xenial)
     Assignee: (unassigned) => dann frazier (dannf)

** Changed in: lshw (Ubuntu)
     Assignee: (unassigned) => dann frazier (dannf)

** Changed in: lshw (Ubuntu Xenial)
   Importance: Undecided => High

-- 
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:
  Confirmed
Status in landscape-client source package in Xenial:
  New
Status in lshw source package in Xenial:
  In Progress

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