From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66713] New: Team Fortress 2 crashes with r600-sb on HD4850
Date: Mon, 08 Jul 2013 21:45:19 +0000 [thread overview]
Message-ID: <bug-66713-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2499 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66713
Priority: medium
Bug ID: 66713
Assignee: dri-devel@lists.freedesktop.org
Summary: Team Fortress 2 crashes with r600-sb on HD4850
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: hubert@kario.pl
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
I'm experiencing TF2 crash when running current (as of today) git master when
specifying R600_DEBUG=sb
the crash occurs as soon as the map is shown (right after the server config was
loaded)
My GPU is Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850]
mesa version:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0-devel
(git-1415a18)
OpenGL core profile shading language version string: 1.40
unfortunately the game's console output isn't really helpful:
Redownloading all lightmaps
m_face->glyph->bitmap.width is 0 for ch:32 TF2
m_face->glyph->bitmap.width is 0 for ch:32 TF2 Professor
m_face->glyph->bitmap.width is 0 for ch:32 TF2
m_face->glyph->bitmap.width is 0 for ch:32 TF2
m_face->glyph->bitmap.width is 0 for ch:32 TF2 Professor
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
Uploading dump (out-of-process) [proxy '']
/tmp/dumps/crash_20130708231132_1.dmp
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
Game removed: AppID 440 "Team Fortress 2", ProcID 619
/mnt/backup/Steam/SteamApps/common/Team Fortress 2/hl2.sh: line 67: 619
Aborted (core dumped) ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE}
"$@"
Generating new string page texture 172: 256x256, total string texture memory is
2.83 MB
Finished uploading minidump (out-of-process): success = yes
response: CrashID=bp-e81b0255-1345-437c-b5e9-47a552130708
Generating new string page texture 178: 24x256, total string texture memory is
2.85 MB
unlinked 2 orphaned pipes
CAsyncIOManager: 0 threads terminating. 0 reads, 0 writes, 0 deferrals.
CAsyncIOManager: 12948 single object sleeps, 0 multi object sleeps
CAsyncIOManager: 0 single object alertable sleeps, 3 multi object alertable
sleeps
the game runs fine for extended periods of time with regular backend
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3865 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-07-08 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 21:45 bugzilla-daemon [this message]
2013-07-08 21:54 ` [Bug 66713] Team Fortress 2 crashes with r600-sb on HD4850 bugzilla-daemon
2013-07-09 23:42 ` bugzilla-daemon
2013-07-13 11:00 ` bugzilla-daemon
2013-07-13 13:23 ` bugzilla-daemon
2013-07-13 23:07 ` bugzilla-daemon
2013-07-14 2:40 ` bugzilla-daemon
2013-07-17 14:49 ` bugzilla-daemon
2013-07-28 13:05 ` 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-66713-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.