All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58655] New: Screen totally corrupted on CAYMAN
Date: Sat, 22 Dec 2012 18:20:34 +0000	[thread overview]
Message-ID: <bug-58655-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]

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

          Priority: medium
            Bug ID: 58655
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Screen totally corrupted on CAYMAN
          Severity: blocker
    Classification: Unclassified
                OS: All
          Reporter: v10lator@myway.de
          Hardware: Other
            Status: NEW
           Version: DRI CVS
         Component: DRM/Radeon
           Product: DRI

This is caused by this mesa commit:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=24b1206ab2dcd506aaac3ef656aebc8bc20cd27a
and kernel 3.8-rc1.

I would love if this could be fixed fast as I have another, more important bug
that I need to test against newest mesa git, which isn't possible as I can't go
above the commit.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2263 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2012-12-22 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22 18:20 bugzilla-daemon [this message]
2012-12-22 19:40 ` [Bug 58655] Screen totally corrupted on CAYMAN bugzilla-daemon
2012-12-22 19:42 ` [Bug 58655] Screen totally corrupted on CAYMAN, [drm : evergreen_vm_reg_valid] *ERROR* Invalid register 0x8040 in CS bugzilla-daemon
2012-12-22 19:42 ` bugzilla-daemon
2012-12-22 20:01 ` bugzilla-daemon
2012-12-24 19:28 ` 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-58655-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.