Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Kenneth Graunke <kenneth@whitecape.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Question about how to troubleshoot sandybridge kernel opps and subsequest GPU lockup
Date: Tue, 25 Oct 2011 09:15:58 +0200	[thread overview]
Message-ID: <20111025091558.214c5c06@jbarnes-x220> (raw)
In-Reply-To: <4EA62260.3070609@whitecape.org>

On Mon, 24 Oct 2011 19:43:44 -0700
Kenneth Graunke <kenneth@whitecape.org> wrote:

> On 10/24/2011 05:58 PM, James R. Leu wrote:
> > Debug output attached
> 
> You're in luck!  I fixed this GPU hang today in Mesa master.
> 
> This commit fixes the hang:
> 
> commit 3cc0a7be23ab603ed40d602595f673a44e079885
> Author: Kenneth Graunke <kenneth@whitecape.org>
> Date:   Fri Oct 21 01:03:37 2011 -0700
> 
>     i965: Apply post-sync non-zero workaround to homebrew workaround.
> 
>     In commit 3e5d3626, Eric added a homebrew workaround to fix GPU
> hangs in the Mesa "engine" demo and oglc's api-texcoord test.
> 
>     Unfortunately, his PIPE_CONTROL contains a Depth Stall, which
>     necessitates the post-sync non-zero workaround,
> 
>     Fixes GPU hangs in Civilization 4, PlaneShift, and 3DMMES.
>     Hopefully Heroes of Newerth as well, though I haven't tested that.
> 
>     NOTE: This is candidate for the 7.11 branch.
> 
>     Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=40324
>     Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=41096
>     Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
>     Reviewed-and-tested-by: Eric Anholt <eric@anholt.net>
> 
> I'm planning on cherry-picking it to the 7.11 branch in the next few
> days, so it ought to make the upcoming 7.11.1 release.

It's good that we have so many ways and opportunities to test our GPU
reset reliability.

Gordon, can you make sure our regular QA covers GPU hang detect and
reset using a few different methods (e.g. the ones above but without
the fix from Ken in Mesa)?  It's important that reset work really well
and ideally w/o even being noticed by the user, so the more ways we
have to wedge things, the better we can test the reset path's
invisibility.

Thanks,
Jesse

  reply	other threads:[~2011-10-25  7:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111024024822.GA5123@mindspring.com>
2011-10-24  4:12 ` Question about how to troubleshoot sandybridge kernel opps and subsequest GPU lockup James R. Leu
2011-10-24  6:46   ` Daniel Vetter
2011-10-25  0:58     ` James R. Leu
2011-10-25  2:43       ` Kenneth Graunke
2011-10-25  7:15         ` Jesse Barnes [this message]
2011-10-25  7:49           ` Daniel Vetter
2011-10-28 14:12 Nicolas Kalkhof
2011-10-28 14:45 ` Bojan Smojver
2011-11-01  1:42   ` James R. Leu
2011-11-01 10:37     ` Eugeni Dodonov
2011-11-01 11:05       ` James R. Leu
  -- strict thread matches above, loose matches on Subject: below --
2011-10-28 14:47 nkalkhof

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=20111025091558.214c5c06@jbarnes-x220 \
    --to=jbarnes@virtuousgeek.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kenneth@whitecape.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