linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: Keith Packard <keithp@keithp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i915 wakes from suspend to RAM with blank screen after commit cd9dde44f47501394b9f0715b6a36a92aa74c0d0
Date: Sat, 21 Jan 2012 19:44:53 +0100	[thread overview]
Message-ID: <20120121184453.GA2698@nbgentoo> (raw)
In-Reply-To: <86mx9gkjlv.fsf@sumi.keithp.com>

On Sat, Jan 21, 2012, 10:15:24, Keith Packard wrote:
> On Sat, 21 Jan 2012 10:32:14 +0000 (UTC), Lubos Kolouch <lubos.kolouch@gmail.com> wrote:
> 
> > 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
> 
> Did you try reverting this single commit on top of 3.3-rc1?
> 
> And, can you collect the dmesg output with the kernel parameter drm.debug=0xe
> added to the boot line, both messages at boot time *and* messages during
> resume would be needed. If it works at boot time, I'm quite surprised it
> somehow doesn't work at resume...

I tried now and when I revert this line :

- return (pixel_clock * bpp + 7) / 8;
+ return (pixel_clock * bpp + 9) / 10;

resume works OK for me with 3.3-rc1.

Before change (failed)
----------------------
dmesg after boot - http://paste.pocoo.org/show/538343/
dmesg after failed resume -  http://paste.pocoo.org/show/538344/

After change (OK)
-----------------
dmesg after boot - http://paste.pocoo.org/show/538345/
dmesg after OK resume - http://paste.pocoo.org/show/538346/

Luboš Kolouch

  reply	other threads:[~2012-01-21 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 10:32 i915 wakes from suspend to RAM with blank screen after commit cd9dde44f47501394b9f0715b6a36a92aa74c0d0 Lubos Kolouch
2012-01-21 18:15 ` Keith Packard
2012-01-21 18:44   ` Lubos Kolouch [this message]
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=20120121184453.GA2698@nbgentoo \
    --to=lubos.kolouch@gmail.com \
    --cc=keithp@keithp.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 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).