mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Commit 500f7147cf5bafd139056d521536b10c2bc2e154 breaks _resume_
Date: Sun, 06 Feb 2011 12:00:15 +0100	[thread overview]
Message-ID: <s5hfws1whq8.wl%tiwai@suse.de> (raw)
In-Reply-To: <AANLkTi=h+H+N=f4m4pE+RZ4n5h7oxQuwzmK-qmmWAGtL@mail.gmail.com>

At Sun, 6 Feb 2011 09:50:51 +0800,
Jeff Chua wrote:
> 
> On Sun, Feb 6, 2011 at 2:24 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> The suspend monster is back! The suspend-to-ram is fine, but upon
> >> resume, screen is blank. Haven't bisected in case someone has also
> >> done so.
> >
> > BTW, please don't reply to messages containing patches with reports of problems
> > that aren't caused by those patches.  It's confusing at best and at worst it
> > may result in the patches being rejected.
> 
> Sorry. New subject now:)
> 
> 
> On Sun, Feb 6, 2011 at 2:51 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >> It's very recent. ... between commit
> >> 831d52bc153971b70e64eccfbed2b232394f22f8 and
> >> 44f2c5c841da1b1e0864d768197ab1497b5c2cc1.
> >
> > Hmm. It's almost certainly one of the DRI patches, but which one? I
> > think bisection is the only way to figure it out. It shouldn't be too
> > bad, since there's only 120 commits in that range.
> >
> > In fact, you can almost certainly just bisect from 89840966c579 to
> > bb5b583b5279, which is just 31 commits and should get you bisected in
> > just five tries or so.
> 
> Yea, I've just done that. It came down to the following commit.
> Reverting it solves the problem. I've gone thru a few cycles, and
> notebook still survives.

Hrm, what is the symptom?  I couldn't find it because you cut off the
thread, and it's not cited.

The commit you mentioned just adds an interface, and the the callbacks
aren't defined.  The real change is either in
  commit f3269058e7a80083dcdf89698bfcd1a6c6f8fd12
    drm/i915/crt: Force the initial probe after reset
or
  commit 5d1d0cc87fc0887921993ea0742932e0c8adeda0
    drm/i915: Reset crtc after resume

Also the fix might interact with
  commit 811aaa55ba21ab37407018cfc01770d6b037d3fb
    drm: Only set DPMS ON when actually configuring a mode


thanks,

Takashi

> 
> Thanks,
> Jeff
> 
> 
> 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
> 
>     Call drm_mode_config_reset() after an invalidation event to restore any
>     cached state to unknown.
> 
>     Tested-by: Takashi Iwai <tiwai@suse.de>
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> 

  parent reply	other threads:[~2011-02-06 11:00 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06  1:50 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 [this message]
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
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=s5hfws1whq8.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=jeff.chua.linux@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®