Re: kerneloops.org report for the week

[Andi Kleen]

Ingo Molnar <mingo@xxxxxxx> writes:
>
>> Rank 8: generic_get_mtrr (warning)
>> 	Reported 544 times (2061 total reports)
>> 	BIOS bug where the MTRRs are not set up correctly
>> 	This warning was last seen in version 2.6.30, and first seen in 2.6.25.3.
>> 	More info: http://www.kerneloops.org/searchweek.php?search=generic_get_mtrr
>
> I think this calls for enabling the x86 MTRR sanitizer by default - 
> 500 out of 15000 reports suggests a significant proportion of Linux 
> systems is affected by MTRR setup problems.

The question is if the MTRRs are really wrong. The generic.c code checks
against the maximum address space reported by the CPU, but the BIOS might
only sets up the address space that is actually used. The later
is not really wrong; it's not needed to set MTRRs for non existing
mappings.

It might be better to double check against the max e820 mapping too
or drop that check.

-Andi

-- 
ak@xxxxxxxxxxxxxxx -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/