Hi team,
I’m having some issues with the Weston container, as sometimes it fails to bring up the desktop. Not sure if it is a Colibri iMX8X only thing. My active DTOs are colibri-imx8x-ad7879-overlay.dts.dtbo
and colibri-imx8x-display-lt161010-overlay.dts.dtbo
, and the screen is working perfectly after touch calibration.
I can bring up the Weston Desktop using the command found here:
docker run -e ACCEPT_FSL_EULA=1 --rm --name=weston --net=host --cap-add CAP_SYS_TTY_CONFIG \
-v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ \
--device-cgroup-rule='c 4:* rmw' --device-cgroup-rule='c 13:* rmw' --device-cgroup-rule='c 199:* rmw' --device-cgroup-rule='c 226:* rmw' \
torizon/arm64v8-debian-weston-vivante:latest --developer weston-launch --tty=/dev/tty7 --user=torizon
This runs well and I get the desktop in the screen, but after closing it (Ctrl+C) and trying to relaunch it sometimes the screen turns to black and the desktop doesn’t come up. After this, I have to restart the module to make Weston come up again.
I could see I couple of things that trigger when this happens:
-
The container takes much longer to close. If this doesn’t happen, the container usually takes only a couple of seconds to close after Ctrl+C.
-
I periodically get an error message on the serial console while the container is up:
[ 129.492754] [drm:drm_atomic_helper_commit_cleanup_done] *ERROR* [CRTC:31:crtc-0] flip_done timed out
It is not hard to get to this status. Usually leaving the container up for a minute or so, and then closing it triggers it. Doesn’t seem to happen if you close it immediately after opening it.
Find attached the log file . I was able to bring up the desktop twice before this happened.
Can you check this? I don’t want to report this as a bug directly in case I’m doing something wrong. Thanks and kind regards,
Alvaro.