Wrong RAM memory size
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
lshw |
New
|
Undecided
|
Unassigned | ||
landscape-client (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
lshw (Ubuntu) |
Fix Released
|
Critical
|
dann frazier | ||
Xenial |
Fix Released
|
High
|
dann frazier |
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://
[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(
Changed in lshw (Ubuntu): | |
importance: | Undecided → Critical |
description: | updated |
Changed in maas: | |
status: | New → Invalid |
1542260 kB is 1506 Mb (1542260 / 024 = 1506.11328)
So free and /proc/meminfo agree. I don't know where you grabbed the 2GiB figure from. Maybe the rest is being used by an onboard video card?
Anyway, not a landscape-client problem, because we grab that information from /proc/meminfo.