From: Daniel Vetter <daniel@ffwll.ch>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Jiri Slaby <jslaby@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: g33: GPU hangs
Date: Wed, 18 Jan 2012 12:43:08 +0100 [thread overview]
Message-ID: <20120118114308.GA4002@phenom.ffwll.local> (raw)
In-Reply-To: <4F16917E.1090401@gmail.com>
On Wed, Jan 18, 2012 at 10:31:42AM +0100, Jiri Slaby wrote:
> On 12/01/2011 01:47 PM, Chris Wilson wrote:
> > On Thu, 01 Dec 2011 13:30:18 +0100, Jiri Slaby <jslaby@suse.cz> wrote:
> >> Hi,
> >>
> >> both yesterday and today, my GPU hung. Both happened when I opened
> >> google front page in firefox.
> >>
> >> I'm running 3.2.0-rc3-next-20111130. Given it happened twice in the past
> >> 24 hours, it looks like a regression from next-20111124. Or is this a
> >> userspace issue (I might updated some packages)?
> >>
> >> i915_error_state dumps from the two hangs are here:
> >> http://www.fi.muni.cz/~xslaby/sklad/panics/915_error_state_0
> >> http://www.fi.muni.cz/~xslaby/sklad/panics/915_error_state_second
> >
> > Both error states contain the same bug: a fence register in conflict
> > with the command stream. The batch is using the buffer at 0x03d0000
> > as an untiled 40x40 rgba buffer with pitch 192. However, a fence
> > register is programmed to
> > fence[3] = 03d00001
> > valid, x-tiled, pitch: 512, start: 0x03d00000, size: 1048576
> >
> > Also note that buffer is also not listed as currently active, so
> > presumably we reused the buffer as tiled (and so reprogrammed the
> > fence registered) before the GPU retired the batch. That sounds eerily
> > similar to this bug:
> >
> > From 2b76187d2f5fc2352e391914b1828f91f93bb356 Mon Sep 17 00:00:00 2001
> > From: Chris Wilson <chris@chris-wilson.co.uk>
> > Date: Tue, 29 Nov 2011 15:12:16 +0000
> > Subject: [PATCH] drm/i915: Only clear the GPU domains upon a successful
> > finish
>
> Hi, do you plan to push this patch upstream? Or am I supposed to not use
> it anymore?
It's on track to get merged to drm-intel-next. I'll probably pick it up in a week
or so.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-01-18 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 12:30 g33: GPU hangs Jiri Slaby
2011-12-01 12:30 ` Jiri Slaby
2011-12-01 12:47 ` Chris Wilson
2011-12-03 22:58 ` Jiri Slaby
2011-12-03 22:58 ` Jiri Slaby
2012-01-18 9:31 ` Jiri Slaby
2012-01-18 9:31 ` Jiri Slaby
2012-01-18 11:43 ` Daniel Vetter [this message]
2012-01-24 14:51 ` new GPU hang [was: g33: GPU hangs] Jiri Slaby
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=20120118114308.GA4002@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.