Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


"FAILED Meminfo total: 3097452 kB DMI total: 4096000 kB Accuracy: 75.00 Memory totals not close enough" 

I recently had some more RAM installed: I had 1GB. I added 2GB, giving a total of 3GB.

As far as I can tell, it is working OK. For example, I use system-load-indicator and it shows credible amounts of memory used.

I have run System Testing a few times since having the additional RAM installed, and it has shown FAILED each time.

"Meminfo total: 3097452 kB" is exactly what I would expect.

"DMI total: 4096000 kB" doesn't make any sense to me. There are at least 3 plausible meanings of DMI on

"Accuracy: 75.00 Memory totals not close enough" doesn't make any sense to me either. Not close enough to what? I can see that

Meminfo/DMI total

which is kind of about 75.00%.

  1. Is this where "75.00%" comes from?

  2. What do all these numbers (above) mean?

  3. In my case, what does FAILED mean?

  4. If applicable, any suggestions about how NOT to get a FAILED result?

I suppose at the moment I need to see if the RAM needs to be reseated or something.

share|improve this question
can you try to make the memtest 1 memory stick at a time? (not together) – Cubiq Sep 4 '13 at 14:21
I don't know @Cubiq. – el_gallo_azul Nov 9 '13 at 4:54
up vote 1 down vote accepted

The Meminfo total: 3097452 kB shows how much RAM your OS can access. So it is 3GB, as you say you have that much memory in your system, so it is fine.

The DMI total: 4096000 kB comes from your BIOS and shows how much memory is installed according to the BIOS.

The Accuracy: 75.00 Memory totals not close enough is just what you thought, the ratio of the two above: Meminfo_total/DMI_total. (rounded down to 2 decimal places)

So this test is for testing if your OS is correctly detecting an using all your available RAM. If the Accuracy is above 90% then the test PASSes, if it is under it FAILs.

You may ask the question: Why is it passing when it is above 90%, shouldn't this test only pass if the accuracy is exactly 100%? Since that would mean that the OS has access to all the installed memory, under 100% means there is a problem.

The answer is that there is a safe situation when the OS doesn't has access to all the installed memory: When you have an integrated device which uses shared memory and the BIOS reserves some memory for this device from the installed RAM. This is usually an integrated VGA card. So if you have an integrated VGA, it is usually perfectly normal that the accuracy is below 100%, so the test passes even with only 90%. Some minimal RAM is also reserved for some BIOS stuff but those are a negligible amount.

You could argue though that 90% is just an arbitrary number, why not 85% or 80%? Yes, it is arbitrary, and I don't know why was exactly 90% chosen for this test.

You can view the source code of this test in /usr/share/checkbox/scripts/memory_compare, it is a simple bash script on 12.04, on later releases it is a python script. You can also run it from there with sudo /usr/share/checkbox/scripts/memory_compare

Now it is clear that you have no problems with your RAM, since you installed 3GB and all is available. So why is this test reporting that you have 4GB installed memory?

Two situations possible:

So to test the second case run sudo dmidecode -t 17, this is how the test gains access to the BIOS data about RAM. Observe the output if it contains only RAM modules. If it outputs other devices, like in the above linked bugreport, and that device has a Size property, then this test will add the size of that device too to the RAM, and the DMI total output will show more RAM than it is available.

This bug was corrected in the later releases, from 12.10. But in 12.04 we have the old bash script with the bug. And the output you wrote in your comment is from this old bash version of the script.

share|improve this answer
Yep sudo dmidecode -t 17 gives a total of 4GB, so "If it outputs other devices, like in the above linked bugreport, and that device has a Size property, then this test will add the size of that device too to the RAM, and the DMI total output will show more RAM than it is available." (I can't work out how to quote) means that it looks like I have that bug. Thanks. – el_gallo_azul Feb 4 '14 at 3:12

Execute the following command for a more detailed mem-overview:

cat /proc/meminfo

Ubuntu usually caches a lot of ram which is still free, but shown by other tools as used. So you need to subtract the value cached: from the output of the above command.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.