Bug 88574

Summary:	VA-API on RV610 crashes my system
Product:	Mesa	Reporter:	User 142 <user142>
Component:	Drivers/Gallium/r600	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description User 142 2015-01-19 08:15:41 UTC

when I start VLC like this:
export LIBVA_DRIVER_NAME=gallium
vlc
and then inside VLC select VA-API as hardware acceleration and then open a video, my screen goes black after a few seconds and my system becomes unresponsive and I have to force poweroff by long pressing the power button.

I am using Arch Linux with the 3.18.2 Kernel and Mesa 10.4.2
My graphics card: Advanced Micro Devices, Inc. [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 XT]

Comment 1 User 142 2015-09-13 08:27:01 UTC

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).

Comment 2 GitLab Migration User 2019-09-18 19:18:59 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/541.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.