From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31391] New: Heroes of Newerth crashes with cs parser error
Date: Thu, 4 Nov 2010 12:47:07 -0700 (PDT) [thread overview]
Message-ID: <bug-31391-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31391
Summary: Heroes of Newerth crashes with cs parser error
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Keywords: regression
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: stephan@ehilb.de
The game Heroes of Newerth (also referred to as HoN) crashes in certain
circumstances with the following error message in dmesg:
[ 1797.294324] [drm:radeon_cs_parser_init] *ERROR* cs IB too big: 26607
[ 1797.294327] [drm:radeon_cs_ioctl] *ERROR* Failed to initialize parser !
It's occuring during normal gameplay in situations with high graphic workload
(as far as I can tell).
I was up until recently using older libs for playing HoN with the r600 driver
and thus noticed this bug as a regression.
It is possible to reproduce the bug quite reliably by following these steps:
1. Start HoN
2. Create a practice game
3. Select a slot and start the game
4. Select any hero and wait for the countdown or skip the countdown by pressing
ready
5. As the game starts, open the test-menu at the top left of the screen and
press the “Spawn”-button right of where it reads “Creeps” multiple times
(~20-30 times). There should be spawning many creeps at your base.
6. Pan the viewport to include as many creeps as possible.
7. Press the “Kill”-button right next to the “Spawn”-button.
8. 1-2 seconds later the game crashes.
9. You notice the error messages in dmesg
Bisecting issued the following bad commit:
e62e5b0922b6554431234a8a71c7aec7cff91864 is the first bad commit
commit e62e5b0922b6554431234a8a71c7aec7cff91864
Author: Andre Maasikas <amaasikas@gmail.com>
Date: Wed Aug 11 14:30:18 2010 +0300
r600: add support for draw_elements_base_vertex
use VTX_BASE_VTX_LOC for offset, last time using INDEX_OFFSET was
probably a wrong register for this
:040000 040000 2daa2236ba96c969c80cd62b1199d0eacb56ecce
376ee1345c8cbbb51c2b1c36cb7adafac276d5d6 M src
I tried to the best of my ability to manually revert the commit and it proved
to be the cause of the bug.
I'm running mesa-git right now with that commit manually reverted and HoN is
running fine.
Note: This might be the same bug as described in this comment:
https://bugs.freedesktop.org/show_bug.cgi?id=25114#c7
Let me know if there is any information missing.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2010-11-04 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 19:47 bugzilla-daemon [this message]
2011-01-07 19:47 ` [Bug 31391] Heroes of Newerth crashes with cs parser error bugzilla-daemon
2011-03-07 19:48 ` [Bug 31391] [RADEON:R600C] heroes of newerth " bugzilla-daemon
2011-03-08 11:38 ` bugzilla-daemon
2011-03-08 19:13 ` 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-31391-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