All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60224] New: Radeon hd6770 graphics artifacts in team fortress 2 with 3.8 kernel
Date: Sun, 03 Feb 2013 12:06:01 +0000	[thread overview]
Message-ID: <bug-60224-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 60224
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Radeon hd6770 graphics artifacts in team fortress 2
                    with 3.8 kernel
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: pontostroy@gmail.com
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 74130
  --> https://bugs.freedesktop.org/attachment.cgi?id=74130&action=edit
tf2

mesa, libdrm, ddx from git
1:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Juniper
XT [AMD Radeon HD 6000 Series]

With kernel <3.8 all looks fine.

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

[-- Attachment #1.2: Type: text/html, Size: 2276 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:[~2013-02-03 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-03 12:06 bugzilla-daemon [this message]
2013-02-04 10:23 ` [Bug 60224] Radeon hd6770 graphics artifacts in team fortress 2 with 3.8 kernel bugzilla-daemon
2013-02-04 12:23 ` bugzilla-daemon
2013-02-13 16:42 ` bugzilla-daemon
2013-02-13 16:42 ` bugzilla-daemon
2013-02-13 17:55 ` bugzilla-daemon
2013-02-13 17:56 ` 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-60224-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.