From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 38581] New: [RADEON:KMS:R600G] wine, counter strike source crashes during gameplay
Date: Wed, 22 Jun 2011 17:44:56 -0700 (PDT) [thread overview]
Message-ID: <bug-38581-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=38581
Summary: [RADEON:KMS:R600G] wine, counter strike source crashes
during gameplay
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: bpaterni@gmail.com
since bug 35051 no longer seems to be a problem for me, I've been able to play
the game somewhat. Now the problem is that the game always crashes during a
firefight. I'm not sure what exactly triggers the crash, but for me this bug is
always reproducible on the first engagement with the enemy (terrorists/counter
terrorists)
Attached should be a complete wine log of the crash. I believe the problematic
portion is up near the middle where a few shaders fail validation:
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #89:
fixme:d3d_shader:print_glsl_info_log error: shader uses too many varying
components (36 > 32)
Hardware is rv770 (HD 4850) being run on mesa (git)
Let me know if I can provide more info.
--
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:[~2011-06-23 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 0:44 bugzilla-daemon [this message]
2011-06-23 0:54 ` [Bug 38581] [RADEON:KMS:R600G] wine, counter strike source crashes during gameplay bugzilla-daemon
2011-06-23 9:47 ` bugzilla-daemon
2011-06-23 10:55 ` bugzilla-daemon
2011-06-23 14:39 ` bugzilla-daemon
2011-06-23 16:06 ` bugzilla-daemon
2011-06-23 17:14 ` bugzilla-daemon
2011-06-26 3:47 ` 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-38581-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 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.