From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27609] New: Regression: r600 CS checker rejects narrow FBO renderbuffers.
Date: Mon, 12 Apr 2010 18:36:55 -0700 (PDT) [thread overview]
Message-ID: <bug-27609-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=27609
Summary: Regression: r600 CS checker rejects narrow FBO
renderbuffers.
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: nbowler@draconx.ca
Created an attachment (id=34944)
--> (https://bugs.freedesktop.org/attachment.cgi?id=34944)
Full kernel log including failure message.
The R600 CS checker recently merged into the mainline kernel breaks rendering
to FBOs with renderbuffers of width <= 48. The height does not matter.
Attempting to run such a program terminates with
drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream.
See dmesg for more info.
and in dmesg:
radeon 0000:03:00.0: r600_cs_track_validate_cb:198 cb pitch (32 x 4 = 128)
invalid
radeon 0000:03:00.0: r600_packet3_check:1109 invalid cmd stream 514
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
Please see the test case attached to bug 27590 for a program which triggers
this issue. The program works on Linux 2.6.33 and with the software
rasterizer. The problem is reproducible with both mesa 7.8.1 and git master,
against latest Linus git kernel.
--
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-13 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 1:36 bugzilla-daemon [this message]
2010-04-13 1:50 ` [Bug 27609] Regression: r600 CS checker rejects narrow FBO renderbuffers bugzilla-daemon
2019-11-19 8:12 ` 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-27609-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.