Weston does not start after upgrade (imx8mmevk machine with 4.19.y kernel)

Weston does not start after upgrade (imx8mmevk machine with 4.19.y kernel)

[Andrey Zhizhikin]

Hello all,

After the recent upgrade of Weston (commit:
a4fdb4074644bda09b46490163886065b4c00aab) I started to receive the
error from G2D on i.MX8M Mini at the start with following output:
-----------------------
Date: 2019-12-18 UTC
[16:51:24.982] weston 6.0.1
               https://wayland.freedesktop.org
               Bug reports to:
https://gitlab.freedesktop.org/wayland/weston/issues/
               Build: 6.0.1-36-g4ee0a1da-dirty g2d-renderer: refine
enable overlay view feature (2019-10-17 12:57:52 +0800)
[16:51:24.982] Command line: /usr/bin/weston
[16:51:24.982] OS: Linux, 4.19.35-1.1.0+g0f9917c56d59, #1 SMP PREEMPT
Wed Oct 30 11:02:38 UTC 2019, aarch64
[16:51:24.982] Using config file '/etc/xdg/weston/weston.ini'
[16:51:24.982] Output repaint window is 16 ms maximum.
[16:51:24.982] Loading module '/usr/lib/libweston-6/drm-backend.so'
[16:51:24.986] initializing drm backend
[16:51:24.991] logind: session control granted
[16:51:24.994] using /dev/dri/card0
[16:51:24.994] DRM: supports universal planes
[16:51:24.994] DRM: supports atomic modesetting
[16:51:24.994] DRM: supports picture aspect ratio
[16:51:24.994] Loading module '/usr/lib/libweston-6/g2d-renderer.so'
[16:51:24.995] g2d_open fail.
[16:51:24.995] g2d_renderer_create faile.
[16:51:24.995] failed to initialize g2d render
-----------------------

If the G2D support is disabled in the /etc/xdg/weston/weston.ini by
commenting the line:
#use-g2d=1

then Weston falls back to use the GL backend, which also fails with
the following output:
-----------------------
Date: 2019-12-18 UTC
[16:56:14.652] weston 6.0.1
               https://wayland.freedesktop.org
               Bug reports to:
https://gitlab.freedesktop.org/wayland/weston/issues/
               Build: 6.0.1-36-g4ee0a1da-dirty g2d-renderer: refine
enable overlay view feature (2019-10-17 12:57:52 +0800)
[16:56:14.653] Command line: /usr/bin/weston
[16:56:14.653] OS: Linux, 4.19.35-1.1.0+g0f9917c56d59, #1 SMP PREEMPT
Wed Oct 30 11:02:38 UTC 2019, aarch64
[16:56:14.653] Using config file '/etc/xdg/weston/weston.ini'
[16:56:14.653] Output repaint window is 16 ms maximum.
[16:56:14.653] Loading module '/usr/lib/libweston-6/drm-backend.so'
[16:56:14.657] initializing drm backend
[16:56:14.663] logind: session control granted
[16:56:14.667] using /dev/dri/card0
[16:56:14.667] DRM: supports universal planes
[16:56:14.667] DRM: supports atomic modesetting
[16:56:14.667] DRM: supports picture aspect ratio
[16:56:14.672] Loading module '/usr/lib/libweston-6/gl-renderer.so'
[16:56:14.704] EGL client extensions: EGL_EXT_client_extensions
               EGL_EXT_platform_base EGL_KHR_platform_wayland
               EGL_EXT_platform_wayland EGL_KHR_platform_gbm
[16:56:14.712] EGL version: 1.5
[16:56:14.712] EGL vendor: Vivante Corporation
[16:56:14.712] EGL client APIs: OpenGL_ES OpenVG
[16:56:14.712] EGL extensions: EGL_KHR_fence_sync EGL_KHR_reusable_sync
               EGL_KHR_wait_sync EGL_KHR_image EGL_KHR_image_base
               EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image
               EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image
               EGL_EXT_image_dma_buf_import
               EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_lock_surface
               EGL_KHR_create_context EGL_KHR_surfaceless_context
               EGL_EXT_create_context_robustness EGL_EXT_buffer_age
               EGL_ANDROID_native_fence_sync EGL_WL_bind_wayland_display
               EGL_WL_create_wayland_buffer_from_image EGL_KHR_partial_update
[16:56:14.712] EGL_KHR_surfaceless_context available
[16:56:14.725] failed to create context
[16:56:14.725] EGL error state: EGL_BAD_ALLOC (0x3003)
[16:56:14.725] EGL error state: EGL_SUCCESS (0x3000)
[16:56:14.725] failed to initialize egl
-----------------------

To me it looks like graphics drivers are broken in the 4.19.y version
(which was also recently upgraded).

I was wondering if anyone else saw this issue and have a clue how to solve it?

Thanks a lot!

-- 
Regards,
Andrey.

Re: Weston does not start after upgrade (imx8mmevk machine with 4.19.y kernel)

[Andrey Zhizhikin]

On Wed, Dec 18, 2019 at 6:01 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
>
> Hello all,
>
> After the recent upgrade of Weston (commit:
> a4fdb4074644bda09b46490163886065b4c00aab) I started to receive the
> error from G2D on i.MX8M Mini at the start with following output:
> -----------------------
> Date: 2019-12-18 UTC
> [16:51:24.982] weston 6.0.1
>                https://wayland.freedesktop.org
>                Bug reports to:
> https://gitlab.freedesktop.org/wayland/weston/issues/
>                Build: 6.0.1-36-g4ee0a1da-dirty g2d-renderer: refine
> enable overlay view feature (2019-10-17 12:57:52 +0800)
> [16:51:24.982] Command line: /usr/bin/weston
> [16:51:24.982] OS: Linux, 4.19.35-1.1.0+g0f9917c56d59, #1 SMP PREEMPT
> Wed Oct 30 11:02:38 UTC 2019, aarch64
> [16:51:24.982] Using config file '/etc/xdg/weston/weston.ini'
> [16:51:24.982] Output repaint window is 16 ms maximum.
> [16:51:24.982] Loading module '/usr/lib/libweston-6/drm-backend.so'
> [16:51:24.986] initializing drm backend
> [16:51:24.991] logind: session control granted
> [16:51:24.994] using /dev/dri/card0
> [16:51:24.994] DRM: supports universal planes
> [16:51:24.994] DRM: supports atomic modesetting
> [16:51:24.994] DRM: supports picture aspect ratio
> [16:51:24.994] Loading module '/usr/lib/libweston-6/g2d-renderer.so'
> [16:51:24.995] g2d_open fail.
> [16:51:24.995] g2d_renderer_create faile.
> [16:51:24.995] failed to initialize g2d render
> -----------------------
>
> If the G2D support is disabled in the /etc/xdg/weston/weston.ini by
> commenting the line:
> #use-g2d=1
>
> then Weston falls back to use the GL backend, which also fails with
> the following output:
> -----------------------
> Date: 2019-12-18 UTC
> [16:56:14.652] weston 6.0.1
>                https://wayland.freedesktop.org
>                Bug reports to:
> https://gitlab.freedesktop.org/wayland/weston/issues/
>                Build: 6.0.1-36-g4ee0a1da-dirty g2d-renderer: refine
> enable overlay view feature (2019-10-17 12:57:52 +0800)
> [16:56:14.653] Command line: /usr/bin/weston
> [16:56:14.653] OS: Linux, 4.19.35-1.1.0+g0f9917c56d59, #1 SMP PREEMPT
> Wed Oct 30 11:02:38 UTC 2019, aarch64
> [16:56:14.653] Using config file '/etc/xdg/weston/weston.ini'
> [16:56:14.653] Output repaint window is 16 ms maximum.
> [16:56:14.653] Loading module '/usr/lib/libweston-6/drm-backend.so'
> [16:56:14.657] initializing drm backend
> [16:56:14.663] logind: session control granted
> [16:56:14.667] using /dev/dri/card0
> [16:56:14.667] DRM: supports universal planes
> [16:56:14.667] DRM: supports atomic modesetting
> [16:56:14.667] DRM: supports picture aspect ratio
> [16:56:14.672] Loading module '/usr/lib/libweston-6/gl-renderer.so'
> [16:56:14.704] EGL client extensions: EGL_EXT_client_extensions
>                EGL_EXT_platform_base EGL_KHR_platform_wayland
>                EGL_EXT_platform_wayland EGL_KHR_platform_gbm
> [16:56:14.712] EGL version: 1.5
> [16:56:14.712] EGL vendor: Vivante Corporation
> [16:56:14.712] EGL client APIs: OpenGL_ES OpenVG
> [16:56:14.712] EGL extensions: EGL_KHR_fence_sync EGL_KHR_reusable_sync
>                EGL_KHR_wait_sync EGL_KHR_image EGL_KHR_image_base
>                EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image
>                EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image
>                EGL_EXT_image_dma_buf_import
>                EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_lock_surface
>                EGL_KHR_create_context EGL_KHR_surfaceless_context
>                EGL_EXT_create_context_robustness EGL_EXT_buffer_age
>                EGL_ANDROID_native_fence_sync EGL_WL_bind_wayland_display
>                EGL_WL_create_wayland_buffer_from_image EGL_KHR_partial_update
> [16:56:14.712] EGL_KHR_surfaceless_context available
> [16:56:14.725] failed to create context
> [16:56:14.725] EGL error state: EGL_BAD_ALLOC (0x3003)
> [16:56:14.725] EGL error state: EGL_SUCCESS (0x3000)
> [16:56:14.725] failed to initialize egl
> -----------------------
>
> To me it looks like graphics drivers are broken in the 4.19.y version
> (which was also recently upgraded).
>
> I was wondering if anyone else saw this issue and have a clue how to solve it?
>
> Thanks a lot!
>
> --
> Regards,
> Andrey.

I've tested the Weston on the Zeus branch and it looks like it is
fully operable. I have Weston starting up with no issues at all, with
use-g2d=1 is set in the config.

Following is the extract from buildhistory which indicates revisions
of relevant components:
-----------------------
# imx8mmevk-fslc-linux
SRCREV_pn-optee-os = "6a52487eb0ff664e4ebbd48497f0d3322844d51d"
SRCREV_pn-kernel-module-qca6174 = "e008d2578b09f1f593f65ede48529a52312e3957"
SRCREV_pn-imx-boot = "dd0234001713623c79be92b60fa88bc07b07f24f"
SRCREV_pn-linux-imx = "1175b59611537b0b451e0d1071b1666873a8ec32"
SRCREV_pn-u-boot-imx = "0d6d8807793e74402e23772062469aeb4808dd48"
SRCREV_pn-kernel-module-qca9377 = "e008d2578b09f1f593f65ede48529a52312e3957"
SRCREV_pn-kernel-module-imx-gpu-viv = "f54dc1486d13d44766cdb6551d094313f077b535"
SRCREV_pn-cryptodev-module = "fd8b15ef1c8398a69a37932ee48c74ab40329a29"

# aarch64-mx8mm-fslc-linux
SRCREV_pn-gstreamer1.0-plugins-good = "a31aabb7581d3f491cd31889d44479bb0f34990b"
SRCREV_pn-imx-gpu-apitrace = "013499c63d9eddd8c792bd8b136991caa3b8a100"
SRCREV_pn-imx-gst1.0-plugin = "0c5f48b3aee473d8c8f3e853eb2078f054caa4d2"
SRCREV_pn-gstreamer1.0-plugins-bad = "0191521ba226904e4b2f84c38e5f6ae75169a18a"
SRCREV_pn-imx-alsa-plugins = "9a63071e7734bd164017f3761b8d1944c017611f"
SRCREV_boostdesc_pn-opencv = "34e4206aef44d50e6bbcd0ab06354b52e7466d26"
SRCREV_contrib_pn-opencv = "2c32791a9c500343568a21ea34bf2daeac2adae7"
SRCREV_ipp_pn-opencv = "32e315a5b106a7b89dbed51c28f8120a48b368b4"
SRCREV_opencv_pn-opencv = "371bba8f54560b374fbcd47e7e02f015ac4969ad"
SRCREV_vgg_pn-opencv = "fccf7cd6a4b12079f73bbfb21745f9babcd4eb1d"
SRCREV_pn-gstreamer1.0 = "d42548da09724ad8cc1aa4f1944607920be2f4c0"
SRCREV_pn-linux-imx-headers = "dfc78102d29f81d9316b281a3b8af3dff95174c8"
SRCREV_pn-imx-gpu-sdk = "d35bac9419895ea516c25e2f36a6084729d9e6ce"
SRCREV_pn-imx-atf = "1cb68fa0a0dd8bc00b9871b51d4c4e1d0a827b2d"
SRCREV_pn-weston = "fb563901657b296c7c7c86d26602a622429e334f"
SRCREV_pn-libdrm = "95645843f59495387a072d48374718f22e69d7a4"
SRCREV_pn-gstreamer1.0-plugins-base = "f62f8ab685e549eefaecdb1e700239a5a408fcad"
-----------------------

Otavio / Tom / Mihai,
Looks like we're hitting a regression in Weston with all recent
upgrades from NXP of all components (Kernel, drivers, Weston, ...).
Can you please have a look at this? I believe a lot of people would be
affected by this once Yocto 3.1 would roll-out and everyone would
start to upgrade.

Thanks a lot!

-- 
Regards,
Andrey.

Re: [meta-freescale] Weston does not start after upgrade (imx8mmevk machine with 4.19.y kernel)

[Otavio Salvador]

On Thu, Dec 19, 2019 at 7:21 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
> On Wed, Dec 18, 2019 at 6:01 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
...
> I've tested the Weston on the Zeus branch and it looks like it is
> fully operable. I have Weston starting up with no issues at all, with
> use-g2d=1 is set in the config.
>
...
> Otavio / Tom / Mihai,
> Looks like we're hitting a regression in Weston with all recent
> upgrades from NXP of all components (Kernel, drivers, Weston, ...).
> Can you please have a look at this? I believe a lot of people would be
> affected by this once Yocto 3.1 would roll-out and everyone would
> start to upgrade.

Please open an issue at GitHub so we can track it and also mention the
referred updates.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

Re: [meta-freescale] Weston does not start after upgrade (imx8mmevk machine with 4.19.y kernel)

[Andrey Zhizhikin]

On Thu, Dec 19, 2019 at 1:07 PM Otavio Salvador
<otavio.salvador@ossystems.com.br> wrote:
>
> On Thu, Dec 19, 2019 at 7:21 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
> > On Wed, Dec 18, 2019 at 6:01 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
> ...
> > I've tested the Weston on the Zeus branch and it looks like it is
> > fully operable. I have Weston starting up with no issues at all, with
> > use-g2d=1 is set in the config.
> >
> ...
> > Otavio / Tom / Mihai,
> > Looks like we're hitting a regression in Weston with all recent
> > upgrades from NXP of all components (Kernel, drivers, Weston, ...).
> > Can you please have a look at this? I believe a lot of people would be
> > affected by this once Yocto 3.1 would roll-out and everyone would
> > start to upgrade.
>
> Please open an issue at GitHub so we can track it and also mention the
> referred updates.

Thanks for the suggestion, I've opened the issue at GitHub
[https://github.com/Freescale/meta-freescale/issues/242] and added a
bit more logging from the working Weston instance.

>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

-- 
Regards,
Andrey.