Messages in this thread | | | Date | Thu, 27 Nov 2008 12:52:36 +0100 | From | Ingo Molnar <> | Subject | Re: oops/warning report for the week of November 26, 2008 |
| |
* Arjan van de Ven <arjan@linux.intel.com> wrote:
> Rank 8: mtrr_trim_uncached_memory (warning) > Reported 227 times (619 total reports) > There is a high number of machines where our MTRR checks > trigger. I suspect we are too picky in accepting the MTRR > configuration.
the warning here means: "the BIOS messed up but we fixed it up for you just fine".
Should we print a DMI descriptor so that it can be tracked back to the bad BIOSen in question? Or should we (partially) silence the warning itself? Those BIOS bugs need fixing really: older kernels will boot up with bad MTRR settings - resulting in a super-slow system or other weirdnesses. We can tone down the message so that it doesnt show up in kerneloops.org. It's up to you.
Ingo
| |