slow graphics after Suspend to RAM
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.
Quoted 4 lines · John Harrigan
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.)
Quoted 3 lines
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
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
* [email protected] (Mar 17, 2011 @ 07:51+0000):
Quoted 9 lines · John Harrigan
Quoted 4 lines
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?
* [email protected] (Mar 17, 2011 @ 07:51+0000):
Quoted 9 lines · John Harrigan
Quoted 4 lines
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.
Quoted 4 lines · John Harrigan
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