From: Chris Wilson <chris@chris-wilson•co.uk>
To: Sedat Dilek <sedat.dilek@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Daniel Vetter <daniel.vetter@ffwll•ch>,
Dave Airlie <airlied@gmail•com>,
DRI <dri-devel@lists•freedesktop.org>,
intel-gfx <intel-gfx@lists•freedesktop.org>,
"s.dilek" <s.dilek@jpberlin•de>
Subject: Re: linux-next: Tree for Aug 13 [ screen corruption in graphical mode ]
Date: Tue, 13 Aug 2013 17:34:39 +0100 [thread overview]
Message-ID: <20130813163439.GA8805@cantiga.alporthouse.com> (raw)
In-Reply-To: <CA+icZUXdS3EuXyGZiS1--rMu6H0ospzCiK_CXgPv8mOk0sMt+Q@mail.gmail.com>
On Tue, Aug 13, 2013 at 06:23:29PM +0200, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 5:59 PM, Sedat Dilek <sedat.dilek@gmail•com> wrote:
> > I have bisected the issue on Linux v3.11-rc5 + drm-intel-nightly:
> >
> > 5456fe3882812aba251886e36fe55bfefb8e8829 is the first bad commit
> > commit 5456fe3882812aba251886e36fe55bfefb8e8829
> > Author: Chris Wilson <chris@chris-wilson•co.uk>
> > Date: Thu Aug 8 14:41:07 2013 +0100
> >
> > drm/i915: Allocate LLC ringbuffers from stolen
> >
> > As stolen objects now behave identically (wrt to default LLC cacheing)
> > as their normal system counterparts, we no longer have to differentiate
> > our usage for ringbuffers. So allocate them from stolen on SNB+ as well.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson•co.uk>
> > Reviewed-by: Ville Syrjälä <ville.syrjala@linux•intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll•ch>
> >
> > :040000 040000 de063a052f39095f4d2f51b49caef9f827df41e8
> > 1c819aa5501a9fcc9912a5c7c037c71b9b9e9a6b M drivers
> >
> > See also attached files!
> >
>
> With the attached revert-patch my system is OK (with my customized X stack).
No indication of a GPU hang? I'm puzzled as to how this ends up with the
scanout being misread.
cat /sys/kernel/debug/dri/0/i915_gem_stolen
cat /sys/kernel/debug/dri/0/i915_gem_framebuffer
would be interesting.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-13 16:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 9:10 linux-next: Tree for Aug 13 [ screen corruption in graphical mode ] Sedat Dilek
2013-08-13 9:14 ` Sedat Dilek
2013-08-13 9:20 ` Sedat Dilek
2013-08-13 9:25 ` Chris Wilson
2013-08-13 9:35 ` Sedat Dilek
2013-08-13 9:39 ` Chris Wilson
2013-08-13 9:47 ` Sedat Dilek
2013-08-13 9:52 ` Chris Wilson
2013-08-13 9:57 ` Sedat Dilek
2013-08-13 14:07 ` Sedat Dilek
2013-08-13 14:45 ` Sedat Dilek
2013-08-13 15:59 ` Sedat Dilek
2013-08-13 16:23 ` Sedat Dilek
2013-08-13 16:34 ` Chris Wilson [this message]
2013-08-13 16:37 ` Sedat Dilek
2013-08-13 17:03 ` Sedat Dilek
2013-08-13 17:13 ` Chris Wilson
2013-08-13 17:53 ` Sedat Dilek
2013-08-13 18:01 ` Chris Wilson
2013-08-13 18:40 ` Sedat Dilek
2013-08-13 18:53 ` Chris Wilson
2013-08-13 19:05 ` Sedat Dilek
2013-08-13 20:10 ` Chris Wilson
2013-08-13 20:16 ` Sedat Dilek
2013-08-13 20:20 ` Chris Wilson
2013-08-13 20:25 ` Sedat Dilek
2013-08-13 20:33 ` Sedat Dilek
2013-08-13 20:52 ` Sedat Dilek
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=20130813163439.GA8805@cantiga.alporthouse.com \
--to=chris@chris-wilson$(echo .)co.uk \
--cc=airlied@gmail$(echo .)com \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=s.dilek@jpberlin$(echo .)de \
--cc=sedat.dilek@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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