All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73792] New: UVD usage with HD makes X11 quite unstable on Samsung ATIV Book Lite 9 (A4-1450 CPU, KABINI graphics))
Date: Sun, 19 Jan 2014 12:57:11 +0000	[thread overview]
Message-ID: <bug-73792-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 73792
          Assignee: dri-devel@lists.freedesktop.org
           Summary: UVD usage with HD makes X11 quite unstable on Samsung
                    ATIV Book Lite 9 (A4-1450 CPU, KABINI graphics))
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: rvdb@cryptolab.net
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

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

I have a Smasung ATIV Bool Lite 9 notebook on which I installed a
Slackware-current system which works roughly well except suspend and UVD
playback.
About the later, I run a Kernel 3.12.8 with less-than-a-week-ago git pulls of
libdrm, glamor, mesa, mesa-glu and xfree-video-ati.
Desktop graphic and compositing work well without glitch and no specific lag.
I use libvdpau 0.7 and less-than-a-week-ago git pulls of ffmpeg, x264 and vlc.
vlc is configured to use VDPAU and this the UVD chip in the processor.
When running SD h264 videos, everything works fine and the CPU usage is low
(less than 75% of total W11/KWin/vlc on a GHz core, that's fine with me).
I get issues when trying to run HD h264 videos. The CPU usage is still fine,
the video starts but after some time, the video hangs, the system becomes
unresponsive then the screen turns black, as displaying a black image, it's a
bit less black then when the screen is turned of.
At this point, either I need to reboot or at some point, the screen seems to
turn of, then light up again and resume where I was, though sometimes the video
remains black and I have to move the VLC slider to get some images. Then the
film can play several seconds then the whole pattern occurs again. And so on
until the system does not resume and I must reboot.
I've attached dmesg, syslog, glxinfo et vdpauinfo outputs.

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

[-- Attachment #1.2: Type: text/html, Size: 3565 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-01-19 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 12:57 bugzilla-daemon [this message]
2014-01-19 12:57 ` [Bug 73792] UVD usage with HD makes X11 quite unstable on Samsung ATIV Book Lite 9 (A4-1450 CPU, KABINI graphics)) bugzilla-daemon
2014-01-19 12:58 ` bugzilla-daemon
2014-01-19 12:58 ` bugzilla-daemon
2015-01-31 15:50 ` bugzilla-daemon
2015-08-02 11:39 ` 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-73792-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.