From: Jani Nikula <jani.nikula@linux.intel.com>
To: Fennec Fox <fennectech@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>Fennec Fox
<fennectech@gmail.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: Intel graphics corruption
Date: Tue, 09 Dec 2014 10:46:01 +0200 [thread overview]
Message-ID: <874mt5jjna.fsf@intel.com> (raw)
In-Reply-To: <CAD1x5BAR53inpaV3wjXLGxWHN5y_LDRWBkLXBoNMW8tROy91bg@mail.gmail.com>
On Tue, 09 Dec 2014, Fennec Fox <fennectech@gmail.com> wrote:
> do you know how to make the intel-drm-nightly kernel mentioned in this
> bugfix id like to use that until 3.19 lands
It's the drm-intel-nightly branch of the upstream drm intel repository
[1]. The patch seems to apply cleanly on 3.18 too. See [2] for kernel
build instructions.
HTH,
Jani.
[1] http://cgit.freedesktop.org/drm-intel
[2] http://kernelnewbies.org/KernelBuild
>
> On Mon, Dec 8, 2014 at 2:26 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> On Fri, Dec 05, 2014 at 11:29:09PM -0600, Fennec Fox wrote:
>>> well on my arch machine with an intel gma 4 graphics card using
>>> xfree86-video-intel im seeing lots of graphics corruption i can
>>> give images it it would help
>>
>> I presume you filed https://bugs.freedesktop.org/show_bug.cgi?id=87065
>> and so know by that this was fixed by
>>
>> commit 656bfa3afc14e45e2d9e1624bf60d79b3beb12f2
>> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Date: Thu Nov 20 09:26:30 2014 +0100
>>
>> drm/i915: Pin tiled objects for L-shaped configs
>>
>> Let's just throw in the towel on this one and take the cheap way out.
>>
>> Based on a patch from Chris Wilson, but checking for a different bit.
>> Chris' patch checked for even bank layout, this one here for a magic
>> bit. Given the evidence we've gathered (not much) both work I think,
>> but checking for the magic bit might be more accurate.
>>
>> Anyway, works on my gm45 here.
>>
>> For paranoi restrict to gen4 (and mobile), since we've only ever seen
>> this on gm45 and i965gm.
>>
>> Also add some debugfs output so that we can skip the tiled swapping
>> tests properly in these cases.
>>
>> v2: Clean up the quirk'ed pin count in free_object to avoid upsetting
>> the WARN_ON. Spotted by Chris.
>> -Chris
>>
>> --
>> Chris Wilson, Intel Open Source Technology Centre
>
>
>
> --
> Fennec
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-12-09 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 5:29 Intel graphics corruption Fennec Fox
2014-12-08 8:26 ` Chris Wilson
2014-12-09 3:52 ` Fennec Fox
2014-12-09 4:16 ` Fennec Fox
2014-12-09 8:46 ` Jani Nikula [this message]
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=874mt5jjna.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=fennectech@gmail.com \
/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