All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28327] New: Latest d-r-t breaks rendering on RV670
Date: Mon, 31 May 2010 03:15:41 -0700 (PDT)	[thread overview]
Message-ID: <bug-28327-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Latest d-r-t breaks rendering on RV670
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: lists@andyfurniss.entadsl.com


Just updated drt to get the last few commits on AGP rv670 and exa rendering is
is trashed. 

xterm contents OK, but window decoration/menus trashed, glxgears no output,
seamonkey display corrupt.

dmesg has lots of errors like -

[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: r600_cs_track_validate_cb offset[0] 0 to big
radeon 0000:02:00.0: r600_packet3_check:1256 invalid cmd stream 635
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (1920 21 4 0 -> 344064 have 163840)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (1024 320 4 0 -> 2621440 have
1310720)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: r600_cs_track_validate_cb offset[0] 0 to big
radeon 0000:02:00.0: r600_packet3_check:1256 invalid cmd stream 635
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (214 60 4 0 -> 67680 have 61440)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (1024 320 4 0 -> -1610612736 have
1310720)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (1024 320 4 0 -> -1610612736 have
1310720)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (1024 320 4 0 -> 2621440 have
1310720)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (1024 320 4 0 -> 5242880 have
1310720)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (507 4 4 0 -> 8384 have 8192)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (1024 320 4 0 -> 5242880 have
1310720)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (507 4 4 0 -> 8384 have 8192)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: r600_cs_track_validate_cb offset[0] 0 to big
radeon 0000:02:00.0: r600_packet3_check:1256 invalid cmd stream 635
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
radeon 0000:02:00.0: texture bo too small (1920 21 4 0 -> 344064 have 163840)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !

-- 
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:[~2010-05-31 10:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 10:15 bugzilla-daemon [this message]
2010-06-01 12:38 ` [Bug 28327] Latest d-r-t breaks rendering on RV670 bugzilla-daemon
2010-06-01 22:16 ` bugzilla-daemon
2010-06-02  4:53 ` bugzilla-daemon
2010-06-02  5:18 ` bugzilla-daemon
2010-06-02 17:52 ` bugzilla-daemon
2010-06-02 19:08 ` bugzilla-daemon
2010-06-07 16:12 ` bugzilla-daemon
2010-06-07 16:39 ` bugzilla-daemon
2010-06-22  0:09 ` bugzilla-daemon
2010-06-22  0:12 ` bugzilla-daemon
2010-06-22  3:35 ` bugzilla-daemon
2010-11-05 14: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-28327-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.