mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Tony Vroon <tony@linx.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Tejun Heo <tj@kernel.org>,
	yinghai@kernel.org
Subject: Re: MTRR setup failure on Fujitsu Lifebook S761
Date: Fri, 26 Aug 2011 14:29:17 -0700	[thread overview]
Message-ID: <1314394157.4729.23.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <1314385315.8356.0.camel@localhost>

On Fri, 2011-08-26 at 12:01 -0700, Tony Vroon wrote:
> On Fri, 2011-08-26 at 09:37 -0700, H. Peter Anvin wrote:
> > Hm, I don't see any evidence of the MTRR sanitizer running at all...
> 
> It is almost as if it failed to find an optimal configuration; does that
> error path not print anything?

MTRR cleanup bails out in mtrr_need_cleanup() if it finds any entry
other than WB or UC. And the first entry you had was write-protect.

There are couple of issues.

a. mtrr_add_page() checks for the type mismatch between the new entry
and any existing entry. _ANY_ is wrong and we should have used
mtrr_type_lookup() in mtrr_add_page(). mtrr_type_lookup() will look at
all the existing MTRR entries and comeup with the right type for a given
range. We should use that instead.

b. And even after fixing 'a', your bios has already setup all the MTRR's
and there are no spare MTRR's available. So we should really sanitize to
makeup some space if we can.

BTW, before all this: you seem to be using PAT and we really shouldn't
depend on the MTRR configuration to get the write-combining behavior if
PAT is used.

And you seem to say, things were _little_ bit better by using a MTRR
script. What do you mean by _little_ ?

Do you still see the original issue of hangcheck timer elapsed and it is
just that the MTRR warning from drm driver disappeared with your MTRR
script?

thanks,
suresh


  reply	other threads:[~2011-08-26 21:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 12:37 Tony Vroon
2011-08-26 16:37 ` H. Peter Anvin
2011-08-26 19:01   ` Tony Vroon
2011-08-26 21:29     ` Suresh Siddha [this message]
2011-08-26 21:39       ` Tony Vroon
2011-08-26 23:40         ` Suresh Siddha
2011-08-27 20:19           ` Tony Vroon
2011-08-26 22:24       ` H. Peter Anvin
2011-08-26 23:51         ` Suresh Siddha
2011-09-02  9:57           ` Tony Vroon
  -- strict thread matches above, loose matches on Subject: below --
2011-07-22  8:12 Tony Vroon
2011-07-25 10:39 ` Tony Vroon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1314394157.4729.23.camel@sbsiddha-desk.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=tony@linx.net \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®