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 88574] VA-API on RV610 crashes my system
Date: Sun, 13 Sep 2015 08:27:01 +0000	[thread overview]
Message-ID: <bug-88574-502-LykfeTjUnP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88574-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from user142@hotmail.com ---
As of kernel 4.1 and mesa 10.6 the system does not crash/hang anymore but I get
the following messages:

radeon: The kernel rejected CS, see dmesg for more information.

and dmesg gives me the following information:

[  422.606081] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
[  422.658136] [drm:radeon_uvd_cs_parse [radeon]] *ERROR* Invalid UVD handle
0x105c0003!
[  422.658167] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
[  436.853008] [drm:radeon_uvd_cs_parse [radeon]] *ERROR* Failed mapping the
UVD message (-22)!

This happens on both VLC with VDPAU and VA-API and also on MPV. The video
sometimes plays and sometimes does not (just black).

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

[-- Attachment #1.2: Type: text/html, Size: 1573 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:[~2015-09-13  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19  8:15 [Bug 88574] VA-API on RV610 crashes my system bugzilla-daemon
2015-09-13  8:27 ` bugzilla-daemon [this message]
2019-09-18 19:18 ` 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-88574-502-LykfeTjUnP@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