From: Jani Nikula <jani.nikula@linux.intel.com>
To: Martin Kepplinger <martink@posteo.de>,
Martin Steigerwald <martin@lichtvoll.de>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Joerg Roedel <jroedel@suse.de>,
Linux kernel <linux-kernel@vger.kernel.org>,
torvalds@linux-foundation.org, daniel.vetter@intel.com
Subject: Re: [BUG][REGRESSION] mangled display since -rc1
Date: Mon, 07 Nov 2016 19:36:53 +0200 [thread overview]
Message-ID: <87h97j8a4q.fsf@intel.com> (raw)
In-Reply-To: <0e7529fa-6f48-fc31-8d25-18a836171d8c@posteo.de>
On Mon, 07 Nov 2016, Martin Kepplinger <martink@posteo.de> wrote:
> Am 2016-11-07 um 17:01 schrieb Martin Steigerwald:
>> Hello.
>>
>> Am Montag, 7. November 2016, 16:34:35 CET schrieb Martin Kepplinger:
>>> Chris Clayton wrote off list and the mentioned patch fixes the problem
>>> for me too, as it does for others. I hope it make it's way into the tree
>>> soon:
>>
>> With 4.9-rc4 I have corruptions that look like the ones reported in this
>> thread.
>>
>> I reported my finding on LKML thread about 3.9-rc4. And in Bugzilla in a bug
>> report with an attachment that shows the same type of corruptions as here in
>> this thread:
>>
>> https://patchwork.freedesktop.org/patch/116808/
>>
>> mentioned in the other bug report and the following LKML thread does not fix
>> the issue for me:
>>
>> Re: [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re:
>> Linux 4.9-rc4)
>> https://lkml.org/lkml/2016/11/6/70
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=177701#c4
That bug conflates two issues, with the main issue being unrelated to
corruption.
>> In my case it looks like this:
>>
>> https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
>>
>>
>> I have a busy week, so I won´t to any bisecting at the moment. I am
>> happy to test another patch during breaks between holding the
>> training, but please point me specifically to what patch to
>> test. Thank you.
>
> this one: I just replaced max with roundup manually:
As I wrote in another thread, the fix has now been pushed to
drm-intel-fixes branch of http://cgit.freedesktop.org/drm-intel. It's
-rc4 plus half a dozen fixes, including "drm/i915: Round tile chunks up
for constructing partial VMAs" which should fix the corruption.
Please try that, and report back. If it doesn't fix the issue, please
file a bug at the freedesktop.org bugzilla.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-11-07 17:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 10:36 [BUG][REGRESSION] mangled display since -rc1 Martin Kepplinger
2016-10-31 10:40 ` Martin Kepplinger
2016-10-31 15:21 ` Joerg Roedel
2016-10-31 20:44 ` Martin Kepplinger
2016-10-31 21:54 ` Joerg Roedel
2016-11-01 11:27 ` Martin Kepplinger
2016-11-01 11:47 ` Jani Nikula
2016-11-06 11:21 ` Thorsten Leemhuis
2016-11-06 11:43 ` Martin Kepplinger
2016-11-06 13:02 ` Martin Kepplinger
2016-11-07 8:24 ` Jani Nikula
2016-11-07 15:34 ` Martin Kepplinger
2016-11-07 16:01 ` Martin Steigerwald
2016-11-07 16:07 ` Martin Kepplinger
2016-11-07 17:36 ` Jani Nikula [this message]
2016-11-13 21:32 ` Martin Kepplinger
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=87h97j8a4q.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=martink@posteo.de \
--cc=regressions@leemhuis.info \
--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;
as well as URLs for NNTP newsgroup(s).