All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Bumiller <e0425955@student.tuwien.ac.at>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Nouveau] [RFC PATCH 5/5] drm/nouveau: gpu lockup recovery
Date: Wed, 25 Apr 2012 13:06:44 +0200	[thread overview]
Message-ID: <4F97DAC4.4060109@student.tuwien.ac.at> (raw)
In-Reply-To: <20120423163257.GA2886@joi.lan>

On 04/23/2012 06:32 PM, Marcin Slusarz wrote:
> You can run fs-discard-exit-2 test first - for me it causes instant GPU lockup.
> 

That's because it's designed (but not supposed) to do that, it also
locks up with the blob, it's a harmless shader infinite loop.

(May be a bug in the MPs or a wrong setting somewhere, but they don't
pop the control flow stack if all but killed pixels of a partially
killed quad remain on the current execution path).

Activated the watchdog on nv50 now, too, if you want to produce the
lockup with current mesa git run with NOUVEAU_SHADER_WATCHDOG=0 (yes
when we use COMPUTE it will have to be deactivated as well).

> Marcin
> _______________________________________________
> Nouveau mailing list
> Nouveau@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
> 

  parent reply	other threads:[~2012-04-25 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 22:18 [RFC PATCH 5/5] drm/nouveau: gpu lockup recovery Marcin Slusarz
2012-04-23  8:43 ` Martin Peres
2012-04-23 16:32   ` Marcin Slusarz
     [not found]     ` <20120423163257.GA2886-OI9uyE9O0yo@public.gmane.org>
2012-04-23 16:56       ` Martin Peres
2012-04-24 19:31         ` Marcin Slusarz
     [not found]           ` <20120424193150.GC2857-OI9uyE9O0yo@public.gmane.org>
2012-04-25  0:32             ` Ben Skeggs
2012-04-25 11:06     ` Christoph Bumiller [this message]
2012-04-23 16:46 ` Martin Peres
2012-04-23 17:33   ` Marcin Slusarz

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=4F97DAC4.4060109@student.tuwien.ac.at \
    --to=e0425955@student.tuwien.ac.at \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=nouveau@lists.freedesktop.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.