Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
Description
E.g. https://lava.automotivelinux.org/scheduler/job/611
This is using the build from
raspberrypi3:~# systemctl status weston.service
● weston.service - Weston Wayland Compositor
Loaded: loaded (/lib/systemd/system/weston.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-09-29 16:01:01 UTC; 7min ago
Main PID: 440 (code=exited, status=1/FAILURE)
Sep 29 16:01:01 raspberrypi3 systemd[1]: Starting Weston Wayland Compositor...
Sep 29 16:01:01 raspberrypi3 systemd[1]: weston.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 16:01:01 raspberrypi3 systemd[1]: Failed to start Weston Wayland Compositor.
Sep 29 16:01:01 raspberrypi3 systemd[1]: weston.service: Unit entered failed state.
Sep 29 16:01:01 raspberrypi3 systemd[1]: weston.service: Failed with result 'exit-code'.
raspberrypi3:~# cat /run/platform/display/weston.log Date: 2018-09-29 UTC [16:06:27.774] weston 2.0.0 http://wayland.freedesktop.org Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=2.0.0 Build: 1.99.94-2-g4c4f13d configure.ac: bump to version 2.0.0 for the official release (2017-02-24 16:19:03 -0800) [16:06:27.774] Command line: /usr/bin/weston --idle-time=0 --tty=1 --log=/run/platform/display/weston.log [16:06:27.774] OS: Linux, 4.9.80, #1 SMP Sat Sep 29 16:19:54 UTC 2018, armv7l [16:06:27.774] Using config file '/etc/xdg/weston/weston.ini' [16:06:27.774] Output repaint window is 7 ms maximum. [16:06:27.775] Loading module '/usr/lib/libweston-2/drm-backend.so' [16:06:27.783] initializing drm backend [16:06:27.784] logind: failed to get session seat [16:06:27.784] logind: cannot setup systemd-logind helper (-61), using legacy fallback [16:06:27.784] fatal: failed to create compositor backend
leonanavi , sdesneux any idea why this might happen (rpi3 + nbd) ?
Display works before (kernel log and such).
Interestingly this seems to work in the CI tests as I see the homescreen on the board come up, I'll look for possible differences in the job descriptions.
Attachments
Issue Links
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
18145,2 | fdtoverlay: Provide fdtoverlay-native | master | AGL/meta-agl | Status: MERGED | +2 | +1 |
18147,2 | create-combined-dtb: Combine dtb and dtbo | master | AGL/meta-agl | Status: MERGED | +2 | +1 |
18305,3 | agl_raspberrypi3.inc: Add create-combined-dtb | master | AGL/meta-agl | Status: MERGED | +2 | +1 |
18321,2 | create-combined-dtb: Add dependency on virtual/kernel | master | AGL/meta-agl | Status: MERGED | +2 | +1 |
18455,1 | fdtoverlay: Provide fdtoverlay-native | flounder | AGL/meta-agl | Status: MERGED | +2 | +1 |
18457,2 | create-combined-dtb: Combine dtb and dtbo | flounder | AGL/meta-agl | Status: MERGED | +2 | +1 |
18459,5 | agl_raspberrypi3.inc: Add create-combined-dtb | flounder | AGL/meta-agl | Status: MERGED | +2 | +1 |
18485,1 | create-combined-dtb: Add dependency on virtual/kernel | flounder | AGL/meta-agl | Status: MERGED | +2 | +1 |
22102,4 | create-combined-dtb: Check if DTB files exist | master | AGL/meta-agl | Status: MERGED | +2 | +1 |
22107,3 | create-combined-dtb: Check if DTB files exist | halibut | AGL/meta-agl | Status: MERGED | +2 | +1 |