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" <yinghai@kernel.org>,
venki@google.com, Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: MTRR setup failure on Fujitsu Lifebook S761
Date: Fri, 26 Aug 2011 16:40:33 -0700 [thread overview]
Message-ID: <1314402034.4729.33.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <1314394765.8356.5.camel@localhost>
On Fri, 2011-08-26 at 14:39 -0700, Tony Vroon wrote:
> On Fri, 2011-08-26 at 14:29 -0700, Suresh Siddha wrote:
> > And you seem to say, things were _little_ bit better by using a MTRR
> > script. What do you mean by _little_ ?
>
> Little in that scrolling in terminals seems to work better. A failure
> mode where the mouse cursor refuses to move seems to occur less often.
Ok. With out your MTRR script and with kernel boot parameter "nopat"
does the perf issue you have seen remain same or becomes further worse?
Perhaps some of the driver mappings are not setting the PAT attribute
correctly or the PAT attribute doesn't help at all. The above experiment
will give us some clue.
> > 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?
>
> Yes, the hangcheck timer checks still fire intermittently and graphics
> performance is still hit & miss. There is a failure mode that I call the
> Amiga loading screen where vertical lines appear that are all a pixel
> wide and are continuously changing in colour.
This one seems to be a different issue that need to be reported to the
graphics folks.
thanks.
>
> The AGP aperture is exactly 256MB in the location that the DRM warning
> complained about, so what I did with the script was an attempt to answer
> its lament. It accept that it may be completely meaningless in practice.
>
> Regards,
> Tony V.
next prev parent reply other threads:[~2011-08-26 23:37 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
2011-08-26 21:39 ` Tony Vroon
2011-08-26 23:40 ` Suresh Siddha [this message]
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=1314402034.4729.33.camel@sbsiddha-desk.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tony@linx.net \
--cc=venki@google.com \
--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®