All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65958] New: GPU Lockup on Trinity 7500G
Date: Thu, 20 Jun 2013 09:18:54 +0000	[thread overview]
Message-ID: <bug-65958-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 65958
          Assignee: dri-devel@lists.freedesktop.org
           Summary: GPU Lockup on Trinity 7500G
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: mike@fireburn.co.uk
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

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

I'm running the latest git from Linus's tree with xf86-video-ati libdrm and
mesa from git

The lockup seems to happen when video is playing. It's Xv rather than vdpau
that seems to cause this

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

[-- Attachment #1.2: Type: text/html, Size: 2236 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-06-20  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  9:18 bugzilla-daemon [this message]
2013-06-20  9:19 ` [Bug 65958] GPU Lockup on Trinity 7500G bugzilla-daemon
2013-06-20 13:37 ` bugzilla-daemon
2013-06-25 13:14 ` bugzilla-daemon
2014-01-02 14:18 ` 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-65958-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.