Bug 109548 - Seeing visual corruption in totem after installing amdgpu 18.50 in Ubuntu 18.04.1
Summary: Seeing visual corruption in totem after installing amdgpu 18.50 in Ubuntu 18....
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
: 106490 (view as bug list)
Depends on:
Reported: 2019-02-04 23:58 UTC by spause+bugzilla
Modified: 2019-07-19 07:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

video (with issue) properties (647.39 KB, image/png)
2019-02-04 23:58 UTC, spause+bugzilla
video (no issues) properties (421.21 KB, image/png)
2019-02-04 23:59 UTC, spause+bugzilla

Note You need to log in before you can comment on or make changes to this bug.
Description spause+bugzilla 2019-02-04 23:58:48 UTC
Created attachment 143292 [details]
video (with issue) properties

Seeing visual corruption in totem after installing amdgpu 18.50 in Ubuntu 18.04.1.  Not present with default OS provided video driver.

I've just tested opening a specific video when my Ubuntu 18.04.1 LTS system does not have the amdgpu driver installed from AMD, and AFTER the driver is installed. 

The video is fine when the default (Ubuntu provided) video driver is used.  After the latest (18.50) AMD video driver (amdgpu) is installed (and computer is rebooted) this attached/linked video displays in bright colors.

See attached example screenshot of video issue/properties. I will try to attach more pics if possible.

If I add the following to the /etc/drirc, the issue disappears.  The word is that this indicates there is an issue with rgb10 support (10 bit RGB or 10bpc ? )

        <application name="Default">
            <option name="allow_rgb10_configs" value="false"/>
Comment 1 spause+bugzilla 2019-02-04 23:59:36 UTC
Created attachment 143293 [details]
video (no issues) properties
Comment 2 spause+bugzilla 2019-02-05 00:04:51 UTC
It seems like this issue is maybe the same as this one associated with Intel driver here - https://bugs.freedesktop.org/show_bug.cgi?id=104536

But I may be misunderstanding.

I will say that the AMDgpu drivers appear to have usability issues in Ubuntu 18.50, as my primary intent is gaming, and there is almost no possible configuration without major side effects. I did try amdgpu-pro,  which caused a whole other set of issues.

I also edit videos almost daily. So I notice issues immediately.

Let me know what detail you require to proceed.  I'm not sure where the issue could be, but mesa was mentioned in a similar bug report (https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312).
Comment 3 Michel Dänzer 2019-02-05 09:00:44 UTC
Most of the time, if disabling allow_rgb10_configs works around an issue like this, it's a bug in the application or a higher level library above Mesa.

However, some people are claiming this is a Mesa issue (something about not (correctly) supporting some VA-API functionality, resulting in the application using a pixel format that can't work).

It most certainly isn't a kernel driver issue, so reassigning to Mesa for now.

Please attach the output of vainfo when the problem occurs.
Comment 4 spause+bugzilla 2019-02-05 23:53:43 UTC
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Mesa Gallium driver 18.2.0-rc3 for Radeon 550 Series (POLARIS12, DRM 3.27.0, 4.15.0-45-generic, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc
Comment 5 Michel Dänzer 2019-02-07 16:17:29 UTC
AMD's Leo Liu confirmed this is a gstreamer-vaapi bug, and posted a description of the problem and a suggestion for a possible fix to the gstreamer development mailing list.
Comment 6 Michel Dänzer 2019-04-01 10:11:59 UTC
*** Bug 106490 has been marked as a duplicate of this bug. ***
Comment 7 Timothy Pearson 2019-07-19 07:28:30 UTC
Do you have a link to the list post?  So far I've identified Chromium and MythTV both as being affected on Polaris GPUs, Chromium may be using gstreamer but I'm not sure about MythTV.  Would like to follow the upstream discussion and see what the resolution is.

Comment 8 Michel Dänzer 2019-07-19 07:52:10 UTC
(In reply to Timothy Pearson from comment #7)
> Do you have a link to the list post?

https://lists.freedesktop.org/archives/gstreamer-devel/2019-February/070435.html => https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/136

> So far I've identified Chromium and MythTV both as being affected on Polaris
> GPUs, Chromium may be using gstreamer but I'm not sure about MythTV.

There are likely similar bugs in other code-bases. It's a bit of a trap in the GLX specification.

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.