memory_compare script doesn't account for all RAM usage

Bug #1019240 reported by Brendan Donegan on 2012-06-29
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Checkbox Provider for PlainBox

Bug Description

Currently the memory_compare script checks dmidecode to see how much RAM is installed on the system and then simply checks the MemTotal field of /proc/meminfo to see if it's accounted for. It appears to be the case on many systems that some RAM is unaccounted for. This is unlikely to be an OS bug so the script should account for other RAM usage, for example by discrete GPUs using it as video memory and make sure it is all used legitimately.

As pointed out in another bug, the Unified Memory Architecture graphics cards can be one reason why we see memory go 'missing'

Changed in checkbox:
status: New → Confirmed
importance: Undecided → High

This false positive is occuring on very few systems now in the SRU testing so I'm lowering the importance to Medium

Changed in checkbox:
importance: High → Medium

In reviewing another merge request I've discovered that a way to view the graphics memory used by a card is in 'lspci -v'. Exploring this as a potential way to account for the 'lost' memory.

Changed in checkbox:
status: Confirmed → In Progress
assignee: nobody → Brendan Donegan (brendan-donegan)
Changed in checkbox:
assignee: Brendan Donegan (brendan-donegan) → nobody
status: In Progress → Confirmed
Daniel Manrique (roadmr) on 2013-06-05
tags: added: scripts
tags: added: saucy
tags: added: ce-qa-concern
Zygmunt Krynicki (zyga) on 2014-04-23
affects: checkbox → plainbox-provider-checkbox
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers