From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109648] AMD Raven hang during va-api decoding
Date: Fri, 15 Feb 2019 22:52:51 +0000 [thread overview]
Message-ID: <bug-109648-502-TMemAli6Pi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109648-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 978 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109648
Michael Eagle <xanto@egaming.ro> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.freedesktop.or
| |g/show_bug.cgi?id=109107
CC| |leoxsliu@gmail.com
--- Comment #1 from Michael Eagle <xanto@egaming.ro> ---
Same behavior happens with both:
kernel-5.0.0-0.rc4.git2.2.fc30.x86_64
kernel-5.0.0-0.rc6.git1.2.fc30.x86_64
Downgrading the kernel to official fedora '4.20.7-200.fc29.x86_64' makes the
system not to crash anymore, however the video is very scrambled, as part of it
would play in a loop.
Disabling 'hardware accelerated video decode' in chrome://flags/ fixes the
issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2347 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-02-15 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 22:15 [Bug 109648] AMD Raven hang during va-api decoding bugzilla-daemon
2019-02-15 22:52 ` bugzilla-daemon [this message]
2019-03-27 12:53 ` bugzilla-daemon
2019-03-27 12:54 ` bugzilla-daemon
2019-03-27 16:43 ` bugzilla-daemon
2019-04-04 19:05 ` bugzilla-daemon
2019-04-04 19:06 ` bugzilla-daemon
2019-04-04 19:07 ` 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-109648-502-TMemAli6Pi@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).