mtrr_cleanup: can not find optimal value and *BAD*gran_size

Solution Unverified - Updated -

Issue

  • mtrr_cleanup: can not find optimal value
  • Below errors in dmesg
*BAD*gran_size: 256M    chunk_size: 512M        num_reg: 7      lose cover RAM: -1M
*BAD*gran_size: 256M    chunk_size: 1G  num_reg: 7      lose cover RAM: -1M
*BAD*gran_size: 256M    chunk_size: 2G  num_reg: 7      lose cover RAM: -1M
 gran_size: 512M        chunk_size: 512M        num_reg: 7      lose cover RAM: 32767M
*BAD*gran_size: 512M    chunk_size: 1G  num_reg: 7      lose cover RAM: -1M
*BAD*gran_size: 512M    chunk_size: 2G  num_reg: 7      lose cover RAM: -1M
 gran_size: 1G  chunk_size: 1G  num_reg: 7      lose cover RAM: 32767M
*BAD*gran_size: 1G      chunk_size: 2G  num_reg: 7      lose cover RAM: -1M
 gran_size: 2G  chunk_size: 2G  num_reg: 7      lose cover RAM: 17407M
mtrr_cleanup: can not find optimal value

Environment

  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content