All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Takashi Iwai <tiwai@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Len Brown <lenb@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Commit 500f7147cf5bafd139056d521536b10c2bc2e154 breaks _resume_
Date: Sun, 6 Feb 2011 22:51:00 +0800	[thread overview]
Message-ID: <AANLkTi=PEhcFYy7Q8e2Dj9p60x2wc=D7vMzR=btEGeUc@mail.gmail.com> (raw)
In-Reply-To: <b9dded$hs5ggh@orsmga002.jf.intel.com>

On Sun, Feb 6, 2011 at 10:47 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Sun, 6 Feb 2011 22:01:22 +0800, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>> It's the commit below. I've checked it twice. Reverting it solves the
>> problem. Suspend to Ram ok. Upon resume, screen is blank. Keyboard
>> hangs. Had to do a hard reset.
>
>> >> commit 500f7147cf5bafd139056d521536b10c2bc2e154
>> >> Author: Chris Wilson <chris@chris-wilson.co.uk>
>> >> Date:   Mon Jan 24 15:14:41 2011 +0000
>> >>
>> >>     drm/i915: Reset state after a GPU reset or resume
>
> Makes no difference to my x201s.
>
> I would have thought a bisection would have resulted in either
> f3269058e7a80083dcdf89698bfcd1a6c6f8fd12 or
> 5d1d0cc87fc0887921993ea0742932e0c8adeda0
>
> Can you try reverting those two to see if either of those is the true
> culprit?

You're too fast. It's the commit below.

commit 5d1d0cc87fc0887921993ea0742932e0c8adeda0
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Jan 24 15:02:15 2011 +0000

    drm/i915: Reset crtc after resume

    Based on a patch by Takashi Iwai.

    Reported-by: Matthias Hopf <mat@mshopf.de>
    Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=27272
    Tested-by: Takashi Iwai <tiwai@suse.de>
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>


Thanks,
Jeff.

  reply	other threads:[~2011-02-06 14:51 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06  1:50 Commit 500f7147cf5bafd139056d521536b10c2bc2e154 breaks _resume_ Jeff Chua
2011-02-06  8:19 ` Marc Koschewski
2011-02-06 11:02   ` Takashi Iwai
2011-02-06 11:06     ` Dave Airlie
2011-02-06 12:21       ` Marc Koschewski
2011-02-06 13:04         ` Rafael J. Wysocki
2011-02-06 13:44           ` Marc Koschewski
2011-02-06 13:55             ` Rafael J. Wysocki
2011-02-06 11:00 ` Takashi Iwai
2011-02-06 12:24   ` Marc Koschewski
2011-02-06 13:19     ` Takashi Iwai
2011-02-06 14:01   ` Jeff Chua
2011-02-06 14:47     ` Chris Wilson
2011-02-06 14:51       ` Jeff Chua [this message]
2011-02-06 14:49     ` Jeff Chua
2011-02-06 15:27       ` Chris Wilson
2011-02-07  4:48         ` Jeff Chua
2011-02-07  5:02           ` Jeff Chua
2011-02-07  8:25             ` Takashi Iwai
2011-02-07  8:36               ` Jeff Chua
2011-02-07  8:45                 ` Jeff Chua
2011-02-07  8:54                   ` Takashi Iwai
2011-02-07  8:52                 ` Takashi Iwai
2011-02-07 10:15                   ` Takashi Iwai
2011-02-07 13:38                     ` Jeff Chua
2011-02-07 14:11                       ` Jeff Chua
2011-02-07 21:20                         ` Rafael J. Wysocki
2011-02-08  1:40                           ` Jeff Chua
2011-02-08 13:36                         ` Chris Wilson
2011-02-09  0:55                           ` Jeff Chua
2011-02-09  1:05                             ` Jeff Chua
2011-02-09  2:56                               ` Indan Zupancic
2011-02-09  5:45                                 ` Jeff Chua
2011-02-09  9:42                                   ` Indan Zupancic
2011-02-09  9:32                                 ` Chris Wilson
2011-02-09 10:20                                   ` Indan Zupancic
2011-02-07 10:02               ` Marc Koschewski
2011-02-07 10:06                 ` Takashi Iwai
2011-02-07 10:09                   ` Marc Koschewski

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='AANLkTi=PEhcFYy7Q8e2Dj9p60x2wc=D7vMzR=btEGeUc@mail.gmail.com' \
    --to=jeff.chua.linux@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=tiwai@suse.de \
    --cc=torvalds@linux-foundation.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.