dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37928] New: foobillard has rendering errors (regression)
Date: Sat,  4 Jun 2011 12:25:08 -0700 (PDT)	[thread overview]
Message-ID: <bug-37928-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=37928

           Summary: foobillard has rendering errors (regression)
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: aaalmosss@gmail.com


Created an attachment (id=47535)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=47535)
foobillard.png

Recently foobillard started to look like on the screenshot. About a month ago
it was fine.

This is written in dmesg:
[  536.002852] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[  536.002859] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[  536.002863] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[  536.014942] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[  536.014950] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[  536.014953] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[  536.017284] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[  536.017292] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[  536.017296] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[  536.020344] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[  536.020352] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[  536.020355] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[  536.051539] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 131072 have 90112) !
[  536.051546] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (256 2 0 256)
[  536.051550] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[  536.142308] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 16384 have 12288) !
[  536.142316] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (256 2 0 32)
[  536.142319] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[  536.223631] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[  536.223639] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[  536.223642] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !


#36934 might be related.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-06-04 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04 19:25 bugzilla-daemon [this message]
2011-06-04 19:32 ` [Bug 37928] foobillard has rendering errors (regression) bugzilla-daemon
2011-06-05 11:40 ` 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-37928-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