From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28860] New: [r300g] Yo Frankie crash: assertion failure / Too many hardware temporaries used
Date: Wed, 30 Jun 2010 13:01:42 -0700 (PDT) [thread overview]
Message-ID: <bug-28860-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28860
Summary: [r300g] Yo Frankie crash: assertion failure / Too many
hardware temporaries used
Product: Mesa
Version: git
Platform: Other
URL: http://www.yofrankie.org/
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: sa@whiz.se
The game "Yo Frankie" crashes if run with shaders turned on:
r300 FP: Compiler Error:
Too many hardware temporaries usedUsing a dummy shader instead.
If there's an 'unknown opcode' message, please file a bug report and attach
this
log.
[...]
yofrankie-linux-i386.bin: state_tracker/st_mesa_to_tgsi.c:181: dst_register:
Assertion `t->outputMapping[index] <
(sizeof(t->outputs)/sizeof(*(t->outputs)))' failed.
I'm attaching a log captured with RADEON_DEBUG="fp".
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: 801e83227a59a29eea425ea612083bbf2b536c30
-- xserver: 1.8.1.901
-- mesa: 75acb896c6da758d03e86f8725d6ca0cb2c6ad82
-- drm: 6ea2bda5f5ec8f27359760ce580fdad3df0464df
-- kernel: 2.6.35-rc3
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-06-30 20:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 20:01 bugzilla-daemon [this message]
2010-06-30 20:03 ` [Bug 28860] [r300g] Yo Frankie crash: assertion failure / Too many hardware temporaries used bugzilla-daemon
2010-06-30 20:07 ` bugzilla-daemon
2010-07-02 20:40 ` bugzilla-daemon
2010-07-02 22:22 ` bugzilla-daemon
2010-07-08 21:50 ` bugzilla-daemon
2010-07-08 21:51 ` [Bug 28860] [r300g] Yo Frankie - shaders not working: Too many instructions bugzilla-daemon
2010-07-09 6:24 ` bugzilla-daemon
2010-07-09 13:46 ` bugzilla-daemon
2010-07-10 20:11 ` bugzilla-daemon
2010-07-11 17:05 ` bugzilla-daemon
2010-07-14 6:10 ` bugzilla-daemon
2010-07-14 19:37 ` bugzilla-daemon
2010-07-15 5:46 ` bugzilla-daemon
2010-07-15 11:58 ` bugzilla-daemon
2010-08-19 14:25 ` bugzilla-daemon
2010-08-20 13:55 ` bugzilla-daemon
2010-08-21 5:48 ` bugzilla-daemon
2010-09-04 10:44 ` bugzilla-daemon
2010-09-04 10:45 ` bugzilla-daemon
2010-09-04 10:47 ` bugzilla-daemon
2010-09-04 10:48 ` bugzilla-daemon
2010-09-08 5:23 ` bugzilla-daemon
2010-09-08 13:58 ` bugzilla-daemon
2010-09-08 22:56 ` bugzilla-daemon
2010-09-08 22:57 ` bugzilla-daemon
2010-09-08 22:58 ` bugzilla-daemon
2010-09-10 22:15 ` bugzilla-daemon
2010-11-13 20:36 ` bugzilla-daemon
2010-11-15 14:02 ` bugzilla-daemon
2010-11-16 2:23 ` bugzilla-daemon
2010-11-16 2:25 ` bugzilla-daemon
2010-11-22 5:50 ` bugzilla-daemon
2010-11-22 19:47 ` bugzilla-daemon
2010-11-22 19:49 ` bugzilla-daemon
2010-11-22 21:14 ` bugzilla-daemon
2010-11-23 1:44 ` bugzilla-daemon
2010-11-24 23:09 ` bugzilla-daemon
2010-11-25 0:03 ` 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-28860-502@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