From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: i915 wakes from suspend to RAM with blank screen after commit cd9dde44f47501394b9f0715b6a36a92aa74c0d0
Date: Sat, 21 Jan 2012 10:32:14 +0000 (UTC) [thread overview]
Message-ID: <jfe47e$5dn$1@dough.gmane.org> (raw)
Hello,
After upgrading kernel from 3.1.5 to 3.2.0 the notebook cannot wake from
suspend to RAM properly. The problem stays even with 3.3-rc1.
It wakes, but the screen is blank and computer needs to be rebooted.
When woken, computer is working otherwise (can ping it, ssh to it etc.)
I git bisected it to commit
cd9dde44f47501394b9f0715b6a36a92aa74c0d0 is the first bad commit
commit cd9dde44f47501394b9f0715b6a36a92aa74c0d0
Author: Adam Jackson <ajax@redhat.com>
Date: Fri Oct 14 12:43:49 2011 -0400
drm/i915/dp: Fix the math in intel_dp_link_required
The previous code was confused about units, which is pretty reasonable
given that the units themselves are confusing.
Signed-off-by: Adam Jackson <ajax@redhat.com>
Signed-off-by: Keith Packard <keithp@keithp.com>
:040000 040000 3c0a0f38fc6482a401340e03fa3fbd687d11eda4
294673b782b3ecc93540f46f7721d385bd30cfac M drivers
Reproducible: Always
Steps to Reproduce:
1. suspend to RAM
2. start the computer
Actual Results:
Screen is blank
Expected Results:
Screen should be normal as before suspend
next reply other threads:[~2012-01-21 10:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 10:32 Lubos Kolouch [this message]
2012-01-21 18:15 ` i915 wakes from suspend to RAM with blank screen after commit cd9dde44f47501394b9f0715b6a36a92aa74c0d0 Keith Packard
2012-01-21 18:44 ` Lubos Kolouch
2012-01-21 20:53 ` Keith Packard
2012-01-22 10:29 ` Lubos Kolouch
2012-01-23 4:00 ` Keith Packard
2012-01-23 6:33 ` Lubos Kolouch
2012-01-26 7:37 ` Keith Packard
2012-01-27 10:14 ` Lubos Kolouch
2012-01-27 18:57 ` Keith Packard
2012-01-31 22:39 ` Joseph Salisbury
2012-02-07 2:31 ` Keith Packard
2012-01-21 18:51 ` Lubos Kolouch
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='jfe47e$5dn$1@dough.gmane.org' \
--to=lubos.kolouch@gmail.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.