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 81192] New: Garbled screen with VDPAU playback and h264
Date: Thu, 10 Jul 2014 20:35:35 +0000	[thread overview]
Message-ID: <bug-81192-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 81192
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Garbled screen with VDPAU playback and h264
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: sige@stripeyc.at
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 102577
  --> https://bugs.freedesktop.org/attachment.cgi?id=102577&action=edit
dmesg output

Whenever I try playing a h264 encoded movie, the system/X11 locks up completely
with 3 different symptoms.
X freezes, I might be able to move the mousecursor (which doesn't change), was
able to log in to the machine remotely and reboot it.
X freezes first, full screen is garbled just a few seconds later.
Additionally I might be able to move some square, which is likely the
"cursor".. garbled as well. I must be honest I didn't try logging in remotely
there yet, if the machine itself is still alive.

Machie is running:
Linux 3.15.4 from the repo and tried on a 3.16rc4 today (Installed that to test
against a kernel bug)
Xorg is 1.15.2
mesa is 10.2.3
mplayer is SVN-r37224

I tried a mpeg2 video and played it just fine
( mplayer -vo vdpau -vc ffmpeg12vdpau <file> )
I also got two h264 files and it freezes/garbles every time there

http://samples.mplayerhq.hu/V-codecs/h264/PAFF/Grey.ts
http://samples.mplayerhq.hu/V-codecs/h264/nature_704x576_25Hz_1500kbits.h264
mplayer -vo vdpau -vc ffh264vdpau <file>

It reliably just freezes the screen, with the mouse working for a while or
completely garbles it.
I also had an occurrence of the screen going garbled and then black, back to
the garbled screen. Three times or something. Maybe he tried resetting the GPU
or something; I don't know. Not sure if I can find any logs from that one.

Also: Haven't tried any other codecs yet, that might be supported.

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

[-- Attachment #1.2: Type: text/html, Size: 3703 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:[~2014-07-10 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 20:35 bugzilla-daemon [this message]
2014-07-10 20:36 ` [Bug 81192] Garbled screen with VDPAU playback and h264 bugzilla-daemon
2014-07-10 20:37 ` bugzilla-daemon
2014-07-10 20:37 ` bugzilla-daemon
2014-07-10 20:48 ` bugzilla-daemon
2014-08-13 15:35 ` bugzilla-daemon
2019-09-18 19:16 ` 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-81192-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