From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27755] New: [KMS] sauerbraten crash with drmRadeonCmdBuffer: -22. -> Vertex array 0 need 83794200 dwords have 112640 dwords
Date: Tue, 20 Apr 2010 08:44:55 -0700 (PDT) [thread overview]
Message-ID: <bug-27755-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=27755
Summary: [KMS] sauerbraten crash with drmRadeonCmdBuffer: -22.
-> Vertex array 0 need 83794200 dwords have 112640
dwords
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: fabio.ped@libero.it
[bug splitted from bug #27507]
I am getting this:
drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See
dmesg for more info.
when starting douze maps with sauerbraten (with shaders enabled).
dmesg shows:
[ 309.795013] radeon 0000:01:00.0: (PW 1) Vertex array 0 need 83794200 dwords
have 112640 dwords
[ 309.795019] [drm:r100_cs_track_check] *ERROR* Max indices 16758840
[ 309.795022] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
I am using current mesa git with:
GL_RENDERER = Mesa DRI R300 (RV530 71C5) 20090101 x86/MMX/SSE2 TCL DRI2
--
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-04-20 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 15:44 bugzilla-daemon [this message]
2010-06-16 3:41 ` [Bug 27755] [KMS] sauerbraten crash with drmRadeonCmdBuffer: -22. -> Vertex array 0 need 83794200 dwords have 112640 dwords bugzilla-daemon
2010-06-16 7:10 ` bugzilla-daemon
2010-11-17 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-27755-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