dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88152] 720p and 1080 H.264 videos lock-up on playback with vlc / vdpau on Radeon 3850HD
Date: Mon, 16 Mar 2015 03:40:12 +0000	[thread overview]
Message-ID: <bug-88152-502-utgfYnhemf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88152-502@http.bugs.freedesktop.org/>


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

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

--- Comment #35 from Arthur Marsh <arthur.marsh@internode.on.net> ---
Created attachment 114333
  --> https://bugs.freedesktop.org/attachment.cgi?id=114333&action=edit
multiple lockup errors immediately after starting video 2015031613dmesg.txt

After upgrading the kernel to 4.0.0-rc4, and vdpau / libdrm:
libvdpau1:amd64                        0.9-1
libdrm-radeon1:amd64                   2.4.59-1

I saw 4 GPU lockup error messages in dmesg (attached) within about half a
second. The video itself locked up a very few seconds into playback. (I could
supply the starting minute of the video if anyone was happy to look at  it).

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

[-- Attachment #1.2: Type: text/html, Size: 1838 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

  parent reply	other threads:[~2015-03-16  3:40 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 11:35 [Bug 88152] 720p and 1080 H.264 videos lock-up on playback with vlc / vdpau on Radeon 3850HD bugzilla-daemon
2015-01-07 11:35 ` bugzilla-daemon
2015-01-07 11:36 ` bugzilla-daemon
2015-01-07 11:37 ` bugzilla-daemon
2015-01-07 14:21 ` bugzilla-daemon
2015-01-11 13:12 ` bugzilla-daemon
2015-01-11 14:47 ` bugzilla-daemon
2015-01-11 15:09 ` bugzilla-daemon
2015-01-12  6:48 ` bugzilla-daemon
2015-01-12 15:11 ` bugzilla-daemon
2015-01-12 15:12 ` bugzilla-daemon
2015-01-13 12:23 ` bugzilla-daemon
2015-01-13 12:25 ` bugzilla-daemon
2015-01-13 12:26 ` bugzilla-daemon
2015-01-13 18:30 ` bugzilla-daemon
2015-01-13 18:31 ` bugzilla-daemon
2015-01-14 11:40 ` bugzilla-daemon
2015-01-14 11:41 ` bugzilla-daemon
2015-01-18 16:42 ` bugzilla-daemon
2015-01-18 16:43 ` bugzilla-daemon
2015-01-19  7:54 ` bugzilla-daemon
2015-01-19  7:56 ` bugzilla-daemon
2015-01-19 11:50 ` bugzilla-daemon
2015-01-21 16:10 ` bugzilla-daemon
2015-01-22 11:55 ` bugzilla-daemon
2015-01-27  2:20 ` bugzilla-daemon
2015-01-27 20:28 ` bugzilla-daemon
2015-01-28  6:12 ` bugzilla-daemon
2015-01-30  2:26 ` bugzilla-daemon
2015-02-07  6:09 ` bugzilla-daemon
2015-02-09  7:22 ` bugzilla-daemon
2015-02-12  8:25 ` bugzilla-daemon
2015-02-12 11:03 ` bugzilla-daemon
2015-02-13  1:45 ` bugzilla-daemon
2015-02-17  9:17 ` bugzilla-daemon
2015-02-17 13:20 ` bugzilla-daemon
2015-03-16  3:40 ` bugzilla-daemon [this message]
2015-04-09 10:41 ` bugzilla-daemon
2015-04-13 13:30 ` bugzilla-daemon
2015-04-16 13:34 ` bugzilla-daemon
2015-05-09 16:14 ` bugzilla-daemon
2015-05-10 10:57 ` bugzilla-daemon
2015-05-11  7:46 ` 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-88152-502-utgfYnhemf@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