All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Blau <eblau@eblau.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Damian Dominik Martinez Dreyer <damian@mailbox.org>,
	intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] Potential BUG in drm/i915/execlists: Reset RING registers upon resume
Date: Wed, 12 Apr 2017 14:55:21 +0200	[thread overview]
Message-ID: <20170412125521.GA10624@kroah.com> (raw)
In-Reply-To: <CADU241Px94Gzk2t0_JSFd_fznZbpChn9DiEMsz+6N9xs3Ujztg@mail.gmail.com>

On Mon, Mar 20, 2017 at 11:24:38AM -0400, Eric Blau wrote:
> On Mon, Mar 20, 2017 at 11:13 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Mon, Mar 20, 2017 at 05:01:34PM +0200, Jani Nikula wrote:
> >> On Tue, 14 Mar 2017, Eric Blau <eblau@eblau.com> wrote:
> >> > That's funny. I have a MacBook Pro 12,1 from late 2015. Hibernate
> >> > failed for me in 4.9.6 through 4.9.8 (possibly earlier as well, I do
> >> > no recall) without the patch. The patch you reference fixed my problem
> >> > and apparently many others based on the bug reports:
> >> >
> >> > https://bugs.freedesktop.org/show_bug.cgi?id=96526
> >> >
> >> > I applied the patch myself in 4.9.6 through 4.9.8 and hibernate works
> >> > for me. I have run vanilla 4.9.9 and 4.10.1 and in both hibernate
> >> > works.
> >>
> >> So I'm quite surprised
> >>
> >> commit f2a0409a08502d64fbe3990354dff5902b08d2fb
> >> Author: Chris Wilson <chris@chris-wilson.co.uk>
> >> Date:   Wed Sep 21 14:51:08 2016 +0100
> >>
> >>     drm/i915/execlists: Reset RING registers upon resume
> >>
> >>     commit bafb2f7d4755bf1571bd5e9a03b97f3fc4fe69ae upstream.
> >>
> >> ended up in v4.9.9 considering that the upstream commit is not annotated
> >> for stable, it has no Fixes: tags, and I can't find any backport
> >> requests or even notifications for it in my mails. (Admittedly I'm not
> >> subscribed on stable@, but I'd expect our lists, maintainers or
> >> developers be Cc'd.)
> >
> > Eric sent this to the stable list a few times, my mistake for not seeing
> > he hadn't also cc:ed the developer list.
> >
> > Want me to revert it?
> >
> > thanks,
> >
> > greg k-h
> 
> My apologies. I'm new to requesting stable patches, but I thought
> sending to the stable mailing lists would keep the proper folks in the
> loop. Sorry about that.
> 
> The bug that the commit fixes has quite a long documentation trail:
> 
> [BAT execlists] Sporadic - gem_exec_suspend basic-s4 GPU hang after resume
> https://bugs.freedesktop.org/show_bug.cgi?id=96526
> 
> I've had problems with that one and this one that is not fixed in 4.10.x stable:
> 
> [Regression BDW] kernel panic in Intel i915 module, complete system
> freeze in 4.10-rc2
> https://bugs.freedesktop.org/show_bug.cgi?id=99295

So, what needs to be done here?

Do I need to revert something in 4.9? Add something?  Do something else?

totally confused,

greg k-h

  reply	other threads:[~2017-04-12 12:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 22:23 Potential BUG in drm/i915/execlists: Reset RING registers upon resume Damian Dominik Martinez Dreyer
2017-03-14  1:20 ` Eric Blau
2017-03-20 15:01   ` Jani Nikula
2017-03-20 15:01     ` [Intel-gfx] " Jani Nikula
2017-03-20 15:13     ` Greg Kroah-Hartman
2017-03-20 15:13       ` [Intel-gfx] " Greg Kroah-Hartman
2017-03-20 15:24       ` Eric Blau
2017-03-20 15:24         ` [Intel-gfx] " Eric Blau
2017-04-12 12:55         ` Greg Kroah-Hartman [this message]
2017-04-12 13:35           ` Jani Nikula
2017-04-12 13:35             ` [Intel-gfx] " Jani Nikula
2017-04-12 13:55             ` Greg Kroah-Hartman
2017-04-12 13:55               ` [Intel-gfx] " Greg Kroah-Hartman
2017-03-20 15:42       ` Jani Nikula
2017-03-20 15:42         ` [Intel-gfx] " Jani Nikula
2017-03-14 11:19 ` Jani Nikula
2017-03-15 22:59   ` Damian Dominik Martinez Dreyer

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=20170412125521.GA10624@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=damian@mailbox.org \
    --cc=eblau@eblau.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=stable@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.