From: Thomas Meyer <thomas@m3y3r.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.16-rc2
Date: Tue, 24 Jun 2014 14:24:30 +0200 [thread overview]
Message-ID: <1403612670.3091.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20140624115753.GD17674@nuc-i3427.alporthouse.com>
Am Dienstag, den 24.06.2014, 12:57 +0100 schrieb Chris Wilson:
> On Tue, Jun 24, 2014 at 02:06:24PM +0300, Jani Nikula wrote:
> > On Tue, 24 Jun 2014, Thomas Meyer <thomas@m3y3r.de> wrote:
> > > the i915 driver is still broken in 3.16-rc2. Resume from ram crashes the
> > > X server.
> >
> > This is not new to 3.16-rc2; apparently we've had it since v3.15-rc4
> > [1]. Also related [2].
> >
> > Chris, any fresh ideas?
>
> Nope. The bug is https://bugs.freedesktop.org/show_bug.cgi?id=76554
> everything we know and have tried is there. Which is not much more than
> at time of the original incarnation:
>
> commit 50aa253d820ad4577e2231202f2c8fd89f9dc4e6
> Author: Keith Packard <keithp@keithp.com>
> Date: Tue Oct 14 17:20:35 2008 -0700
>
> i915: Fix up ring initialization to cover G45 oddities
>
> G45 appears quite sensitive to ring initialization register writes,
> sometimes leaving the HEAD register with the START register contents. Check
> to make sure HEAD is reset correctly when START is written, and fix it up,
> screaming loudly.
> -Chris
>
Hi,
so why not revert 78f2975eec9faff353a6194e854d3d39907bab68 (drm/i915:
Move all ring resets before setting the HWS page) ?
Without this commit 3.15 is super stable for me. This seems to be also
true for others according to above bug report.
thomas
next prev parent reply other threads:[~2014-06-24 12:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+55aFxdAhp-esuGiY4VEugiiwcMJgg1r6fPiR9Fb+HOz_5tLg@mail.gmail.com>
2014-06-23 23:07 ` Linux 3.16-rc2 Thomas Meyer
2014-06-24 11:06 ` Jani Nikula
2014-06-24 11:57 ` Chris Wilson
2014-06-24 12:24 ` Thomas Meyer [this message]
2014-06-24 12:27 ` Chris Wilson
2014-06-30 10:02 ` Pavel Machek
2014-06-30 10:09 ` Chris Wilson
2014-07-02 16:18 ` Thomas Meyer
2014-07-07 15:16 ` Daniel Vetter
2014-07-07 15:32 ` Jiri Kosina
2014-07-07 16:04 ` Chris Wilson
2014-07-07 22:15 ` Jiri Kosina
2014-07-08 8:35 ` Daniel Vetter
2014-07-08 8:59 ` Chris Wilson
2014-07-08 12:46 ` Jiri Kosina
2014-07-08 12:55 ` Chris Wilson
2014-07-08 12:59 ` Jiri Kosina
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=1403612670.3091.10.camel@localhost.localdomain \
--to=thomas@m3y3r.de \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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