dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
Date: Mon, 09 Apr 2012 19:59:12 +0000	[thread overview]
Message-ID: <bug-48472-502-NPbV4vwxmz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-48472-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=48472

--- Comment #2 from Vadim <ptpzz@yandex.ru> 2012-04-09 12:59:12 PDT ---
Created attachment 59693
  --> https://bugs.freedesktop.org/attachment.cgi?id=59693
[PATCH] r600g: check gpr count limit

The problem is that some shader requires too much registers. I suspect it's
caused by the loop unrolling. TGSI source for that shader uses 161 temps.

This patch doesn't solve the real problem, but it will prevent the lockups with
r600g and allow to detect the problem by printing the error message. Also it
may allow the app to run almost as expected (maybe with minor rendering
problems).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-04-09 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 17:12 [Bug 48472] New: GPU Lockup while running demo in wine bugzilla-daemon
2012-04-09 17:19 ` [Bug 48472] " bugzilla-daemon
2012-04-09 18:50 ` [Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) " bugzilla-daemon
2012-04-09 19:59 ` bugzilla-daemon [this message]
2012-04-09 21:03 ` bugzilla-daemon
2012-04-09 21:04 ` bugzilla-daemon
2012-04-09 21:05 ` bugzilla-daemon
2016-06-24 13:10 ` bugzilla-daemon

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=bug-48472-502-NPbV4vwxmz@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox