dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64867] New: Hangs on Cayman (HD6950) when watching flash/using vdpau
Date: Wed, 22 May 2013 14:13:03 +0000	[thread overview]
Message-ID: <bug-64867-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 64867
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Hangs on Cayman (HD6950) when watching flash/using
                    vdpau
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: serafean@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 79658
  --> https://bugs.freedesktop.org/attachment.cgi?id=79658&action=edit
dmesg after X freeze

When watching a flash video (opera + flash-11.2.202.262 ) the kernel log starts
filling up with 
[ 7009.603310] radeon 0000:01:00.0: GPU fault detected: 146 0x0e677004
[ 7009.603313] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
[ 7009.603316] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000

to sometimes eventually hang the GPU. When this starts appearing there is
graphic corruption everywhere. I also managed to reproduce this when playing
back a video using mplayer with the vdpau backend. ( EnableLinuxHWVideoDecode=1
is commented out in /etc/adobe/mms.cfg)

I managed to get a dmesg output after the GPU hang (attached) and then tried to
save what is in /sys/kernel/debug/dri/0 but not knowing which was important,
tried to do it in a bash for cycle, and got a complete hang.

linux-3.10-rc1
mesa, libdrm, radeon ddx from git.

might be related to https://bugs.freedesktop.org/show_bug.cgi?id=62959 , but
piglit just finished fine. (fine = didn't hang in this case, still a bunch of
"radeon_gem_object_create:69 alloc size 1365Mb bigger than 256Mb limit" in the
logs).
Additional info : I have a dual screen setup.

Anything more you need, I'll be happy to provide.

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

[-- Attachment #1.2: Type: text/html, Size: 3546 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-05-22 14:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 14:13 bugzilla-daemon [this message]
2013-05-22 14:26 ` [Bug 64867] Hangs on Cayman (HD6950) when watching flash/using vdpau bugzilla-daemon
2013-06-03 23:33 ` bugzilla-daemon
2013-06-04  0:27 ` bugzilla-daemon
2013-06-06 19:42 ` bugzilla-daemon
2013-06-06 20:58 ` bugzilla-daemon
2013-06-06 21:11 ` bugzilla-daemon
2013-06-16 18:36 ` bugzilla-daemon
2013-06-16 18:39 ` bugzilla-daemon
2013-06-16 18:47 ` bugzilla-daemon
2013-09-14  2:42 ` bugzilla-daemon
2015-01-27 10:27 ` 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-64867-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;
as well as URLs for NNTP newsgroup(s).