From: Jani Nikula <jani.nikula@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>,
Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
dri-devel <dri-devel@lists.freedesktop.org>,
kernel list <linux-kernel@vger.kernel.org>,
Jiri Kosina <jikos@jikos.cz>
Subject: Re: [bisect result] Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
Date: Fri, 25 Apr 2014 14:33:14 +0300 [thread overview]
Message-ID: <87eh0lve2t.fsf@intel.com> (raw)
In-Reply-To: <20140424220638.GA29385@atrey.karlin.mff.cuni.cz>
On Fri, 25 Apr 2014, Pavel Machek <pavel@ucw.cz> wrote:
>> On Thu, Apr 24, 2014 at 09:40:38PM +0200, Pavel Machek wrote:
>> > Hi!
>> >
>> > > And if you can indeed reliably reproduce this a bisect could be really useful.
>> >
>> > And we have a winner here :-)
>> >
>> > Ok, it was not as painfull as I feared.
>> >
>> > It does not revert cleanly, but doing it by hand was not that bad.
>>
>> Oh my. That is bizarre, can you check whether you have
>>
>> commit 9991ae787a0c87fe7c783b4b6f4754c3cdbb6213
>
> Yes, with that commit, graphics is back to working state. Please push
> it to mainline soon -- it fixes a regression. Feel free to add
>
> Tested-by: Pavel Machek <pavel@ucw.cz>
I cherry-picked and pushed
commit 9991ae787a0c87fe7c783b4b6f4754c3cdbb6213
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
to -fixes. Thanks for testing.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-04-25 11:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 20:22 3.15-rc2: i915 regression: only top 20% of screen works in X Pavel Machek
2014-04-23 21:09 ` Daniel Vetter
2014-04-23 22:03 ` Pavel Machek
2014-04-23 22:09 ` Pavel Machek
2014-04-24 5:50 ` Chris Wilson
2014-04-24 6:03 ` Daniel Vetter
2014-04-24 13:36 ` Pavel Machek
2014-04-24 13:56 ` Jiri Kosina
2014-04-24 13:43 ` Pavel Machek
2014-04-24 15:03 ` Chris Wilson
2014-04-24 19:28 ` [partial bisect] " Pavel Machek
2014-04-24 19:40 ` [bisect result] " Pavel Machek
2014-04-24 20:15 ` Chris Wilson
2014-04-24 22:00 ` Pavel Machek
2014-04-24 22:06 ` Pavel Machek
2014-04-24 22:15 ` Jiri Kosina
2014-04-25 11:33 ` Jani Nikula [this message]
2014-04-24 20:13 ` [PATCH] fix " Pavel Machek
2014-04-24 10:42 ` 3.15-rc2: " Pavel Machek
2014-04-24 11:39 ` 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=87eh0lve2t.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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