From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99158] vdpau segfaults and gpu locks with kodi on R9285
Date: Tue, 20 Dec 2016 11:22:39 +0000 [thread overview]
Message-ID: <bug-99158-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1891 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99158
Bug ID: 99158
Summary: vdpau segfaults and gpu locks with kodi on R9285
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: adf.lists@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 128583
--> https://bugs.freedesktop.org/attachment.cgi?id=128583&action=edit
some segfaults
This is an initial report no bisects as I have no clue when it started yet.
It seems there is an unlucky timing situation with kodi that may segfault
radeonsi or lock gpu playing videos with vdpau h/w decode + temporal vdpau
deint which is default kodi settings.
I can't reproduce with mplayer or mpv.
It seems to need HD interlaced + deint, but that may be just because it changes
timing.
Running with VDPAU_TRACE=1 so far avoids the crash/lock, as does setting cpus
to perf.
Running kodi git, but it's reproducable with 11 month old git as well.
It's easiest to provoke starting kodi with a file on command line, but is
possible starting from running kodi menu - possible improved chance of
crash/lock by moving mouse after clicking file to make overlay instantly render
over video.
Attaching some segfaults and locks.
I am running git mesa/llvm/kernel and the crash is rare enough that I may have
missed it for ages given the amount I test kodi. Additionally the best way to
provoke = repeated command line start, only started being possible again
ecently due to a kodi bug.
The segfaults are a bit random.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3384 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-12-20 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 11:22 bugzilla-daemon [this message]
2016-12-20 11:23 ` [Bug 99158] vdpau segfaults and gpu locks with kodi on R9285 bugzilla-daemon
2016-12-20 14:41 ` bugzilla-daemon
2016-12-22 0:00 ` bugzilla-daemon
2016-12-29 11:03 ` bugzilla-daemon
2017-01-04 9:02 ` bugzilla-daemon
2017-01-04 10:18 ` bugzilla-daemon
2017-01-04 10:49 ` bugzilla-daemon
2017-01-05 0:00 ` bugzilla-daemon
2017-01-05 10:51 ` 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-99158-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