From: John Harrigan <jfharrigan@fedex.com>
To: intel-gfx@lists.freedesktop.org
Subject: slow graphics after Suspend to RAM
Date: Wed, 16 Mar 2011 17:59:20 -0600 [thread overview]
Message-ID: <20110316235920.GA392@ink.rmtc.fedex.com> (raw)
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.
next reply other threads:[~2011-03-17 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 23:59 John Harrigan [this message]
2011-03-17 7:51 ` slow graphics after Suspend to RAM Chris Wilson
2011-03-17 15:32 ` John Harrigan
2011-04-13 13:11 ` John Harrigan
2011-03-18 18:44 ` Tino Keitel
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=20110316235920.GA392@ink.rmtc.fedex.com \
--to=jfharrigan@fedex.com \
--cc=intel-gfx@lists.freedesktop.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