intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
* slow graphics after Suspend to RAM
@ 2011-03-16 23:59 John Harrigan
  2011-03-17  7:51 ` Chris Wilson
  2011-03-18 18:44 ` Tino Keitel
  0 siblings, 2 replies; 5+ messages in thread
From: John Harrigan @ 2011-03-16 23:59 UTC (permalink / raw)
  To: intel-gfx

I have a Lenovo X201 laptop with an i7-620M processor.  After I resume
from a Suspend to RAM the graphics are very slow.  Suspend to Disk does
not cause the same problem and doing a Suspend to Disk after a Suspend
to RAM fixes the problem.

I see the same slow-down regardless of whether X11 is running or not.
I'm not doing 3D, I notice the slow-down in regular 2D stuff like
scrolling a lot of text through a terminal window.  When X11 is running
I see the same problem whether I'm using the laptop's display or an
external displayport monitor.  I've tried a 2.6.36 kernel and the
2.6.38 kernel.

Any help in tracking down this problem would be appreciated, Thanks.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: slow graphics after Suspend to RAM
  2011-03-16 23:59 slow graphics after Suspend to RAM John Harrigan
@ 2011-03-17  7:51 ` Chris Wilson
  2011-03-17 15:32   ` John Harrigan
  2011-04-13 13:11   ` John Harrigan
  2011-03-18 18:44 ` Tino Keitel
  1 sibling, 2 replies; 5+ messages in thread
From: Chris Wilson @ 2011-03-17  7:51 UTC (permalink / raw)
  To: John Harrigan, intel-gfx

On Wed, 16 Mar 2011 17:59:20 -0600, John Harrigan <jfharrigan@fedex.com> wrote:
> I have a Lenovo X201 laptop with an i7-620M processor.  After I resume
> from a Suspend to RAM the graphics are very slow.  Suspend to Disk does
> not cause the same problem and doing a Suspend to Disk after a Suspend
> to RAM fixes the problem.

Known problem. The PAT lose the WC bits for the GTT aperture on resume.
There is a workaround that we can do: recreate the ioremapping upon
resume. (But the root cause is not a gfx driver bug.)
 
> I see the same slow-down regardless of whether X11 is running or not.
> I'm not doing 3D, I notice the slow-down in regular 2D stuff like
> scrolling a lot of text through a terminal window.

That's not regular 2D stuff, that's CPU fallback! You will only see a
slight performance difference (an order of magnitude and more, with
comparable decrease in power consumption whilst drawing) by switching to
the XRender paths in your terminal.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: slow graphics after Suspend to RAM
  2011-03-17  7:51 ` Chris Wilson
@ 2011-03-17 15:32   ` John Harrigan
  2011-04-13 13:11   ` John Harrigan
  1 sibling, 0 replies; 5+ messages in thread
From: John Harrigan @ 2011-03-17 15:32 UTC (permalink / raw)
  To: intel-gfx

* chris@chris-wilson.co.uk (Mar 17, 2011 @ 07:51+0000):
> On Wed, 16 Mar 2011 17:59:20 -0600, John Harrigan <jfharrigan@fedex.com> wrote:
> > I have a Lenovo X201 laptop with an i7-620M processor.  After I resume
> > from a Suspend to RAM the graphics are very slow.  Suspend to Disk does
> > not cause the same problem and doing a Suspend to Disk after a Suspend
> > to RAM fixes the problem.
> 
> Known problem. The PAT lose the WC bits for the GTT aperture on resume.
> There is a workaround that we can do: recreate the ioremapping upon
> resume. (But the root cause is not a gfx driver bug.)

Thanks.  Is there an existing bug report somewhere where I should
supply logs and debug info?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: slow graphics after Suspend to RAM
  2011-03-16 23:59 slow graphics after Suspend to RAM John Harrigan
  2011-03-17  7:51 ` Chris Wilson
@ 2011-03-18 18:44 ` Tino Keitel
  1 sibling, 0 replies; 5+ messages in thread
From: Tino Keitel @ 2011-03-18 18:44 UTC (permalink / raw)
  To: intel-gfx

On Wed, Mar 16, 2011 at 17:59:20 -0600, John Harrigan wrote:
> I have a Lenovo X201 laptop with an i7-620M processor.  After I resume
> from a Suspend to RAM the graphics are very slow.  Suspend to Disk does
> not cause the same problem and doing a Suspend to Disk after a Suspend
> to RAM fixes the problem.

I also get this on my ThinkPad X61s using i965 graphics, xorg-intel
2.14 and kernel 2.6.38. Compositing is disabled.

When it happens, drawing of the window title is very slow when changing
window focus, scrolling in gtk windows lags etc.

I also get this after suspend to disk. I can fix it by running
powertop.

Regards,
Tino

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: slow graphics after Suspend to RAM
  2011-03-17  7:51 ` Chris Wilson
  2011-03-17 15:32   ` John Harrigan
@ 2011-04-13 13:11   ` John Harrigan
  1 sibling, 0 replies; 5+ messages in thread
From: John Harrigan @ 2011-04-13 13:11 UTC (permalink / raw)
  To: intel-gfx

* chris@chris-wilson.co.uk (Mar 17, 2011 @ 07:51+0000):
> On Wed, 16 Mar 2011 17:59:20 -0600, John Harrigan <jfharrigan@fedex.com> wrote:
> > I have a Lenovo X201 laptop with an i7-620M processor.  After I resume
> > from a Suspend to RAM the graphics are very slow.  Suspend to Disk does
> > not cause the same problem and doing a Suspend to Disk after a Suspend
> > to RAM fixes the problem.
> 
> Known problem. The PAT lose the WC bits for the GTT aperture on resume.
> There is a workaround that we can do: recreate the ioremapping upon
> resume. (But the root cause is not a gfx driver bug.)

I've opened a bug against memory management for this.

https://bugzilla.kernel.org/show_bug.cgi?id=31372

Chris, I tried to add you as a copy but I may not have done it
correctly.  Could you take a look to see if there's anything
else that could be added?  Thanks.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-04-13 13:26 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-16 23:59 slow graphics after Suspend to RAM John Harrigan
2011-03-17  7:51 ` Chris Wilson
2011-03-17 15:32   ` John Harrigan
2011-04-13 13:11   ` John Harrigan
2011-03-18 18:44 ` Tino Keitel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).