From: Thomas Meyer <thomas@m3y3r.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Dave Airlie <airlied@gmail.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] 3.15-rc5: Regression in i915 driver?
Date: Sun, 18 May 2014 21:08:40 +0200 [thread overview]
Message-ID: <1400440120.3400.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20140512063355.GA3813@nuc-i3427.alporthouse.com>
Am Montag, den 12.05.2014, 07:33 +0100 schrieb Chris Wilson:
> On Sun, May 11, 2014 at 07:40:57PM +0200, Daniel Vetter wrote:
> > On Sun, May 11, 2014 at 11:02 AM, Dave Airlie <airlied@gmail.com> wrote:
> > > On 11 May 2014 18:28, Thomas Meyer <thomas@m3y3r.de> wrote:
> > >> Hi,
> > >>
> > >> 3.14.3 works as expected.
> > >> 3.15-rc5 shows a strange behaviour: When resuming from ram the X server
> > >> seems to be disfunctional.
> > >>
> > >> I see this WARNING in the kernel log before suspend to ram in the early
> > >> boot process:
> >
> > Doesn't ring a bell really.
>
> Same symptoms as
> https://bugs.freedesktop.org/show_bug.cgi?id=76554
> -Chris
>
bisected this to:
# first bad commit: [78f2975eec9faff353a6194e854d3d39907bab68] drm/i915: Move all ring resets before setting the HWS page
commit 78f2975eec9faff353a6194e854d3d39907bab68
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Wed Apr 2 16:36:07 2014 +0100
drm/i915: Move all ring resets before setting the HWS page
In commit a51435a3137ad8ae75c288c39bd2d8b2696bae8f
Author: Naresh Kumar Kachhi <naresh.kumar.kachhi@intel.com>
Date: Wed Mar 12 16:39:40 2014 +0530
drm/i915: disable rings before HW status page setup
we reordered stopping the rings to do so before we set the HWS register.
However, there is an extra workaround for g45 to reset the rings twice,
and for consistency we should apply that workaround before setting the
HWS to be sure that the rings are truly stopped.
Reference: http://lkml.kernel.org/r/20140423202248.GA3621@amd.pavel.ucw.cz
Tested-by: Pavel Machek <pavel@ucw.cz>
Cc: Naresh Kumar Kachhi <naresh.kumar.kachhi@intel.com>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reverting above commit from current linus' master tree makes the display server behave correctly after resume from ram.
with kind regards
thomas
next prev parent reply other threads:[~2014-05-18 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 8:28 3.15-rc5: Regression in i915 driver? Thomas Meyer
2014-05-11 9:02 ` Dave Airlie
2014-05-11 17:40 ` Daniel Vetter
2014-05-12 6:33 ` [Intel-gfx] " Chris Wilson
2014-05-12 16:52 ` Daniel Vetter
2014-05-18 19:08 ` Thomas Meyer [this message]
2014-05-18 19:13 ` Chris Wilson
2014-05-19 7:07 ` Daniel Vetter
2014-06-14 15:30 ` Thomas Meyer
2014-05-12 7:09 ` Jani Nikula
2014-05-12 16:54 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2014-05-17 17:43 Thomas Meyer
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=1400440120.3400.5.camel@localhost.localdomain \
--to=thomas@m3y3r.de \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--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