weston does not startup on rpi3 when booted over nbd
Description
Environment
None
Attachments
1
- 13 Nov 2018, 01:58 PM
Activity
Kevin Hilman December 11, 2018 at 6:27 PM
Kevin Hilman
December 11, 2018 at 6:27 PM
Patches merged, and verified to be working both on guppy and master.
Closing.
Kevin Hilman December 6, 2018 at 4:50 PM
Kevin Hilman
December 6, 2018 at 4:50 PM
OK, here's a run with the cmdline for the CI job updated to match the SD boot: https://lava.automotivelinux.org/scheduler/job/1866
Looks much better, and the weston.service is starting normally.
Patch submitted to update cmdline for CI jobs: https://gerrit.automotivelinux.org/gerrit/#/c/18611/
Tom Rini December 6, 2018 at 2:57 PM
Tom Rini
December 6, 2018 at 2:57 PM
Thanks @Leon Anavi. It looks like we have:
[ 0.000000] Kernel command line: console=ttyS0,115200n8 rw nbd.server=192.168.111.1 nbd.port=61962 root=/dev/ram0 ramdisk_size=16384 rootdelay=7 8250.nr_uarts=1 bcm2709.uart_clock=48000000 smsc95xx.macaddr=AA:BB:CC:DD:EE:AA ip=dhcp verbose earlyprintk systemd.log_color=false ${extraargs} rwBeing set / passed in LAVA via an explicit setenv, so I think that particular part of the LAVA setup needs to be changed @Kevin Hilman.
Leon Anavi December 6, 2018 at 9:56 AM
Leon Anavi
December 6, 2018 at 9:56 AM
Yes, it is 256M. Here is the whole cmd line on Raspberry Pi 3:
raspberrypi3:~# cat /proc/cmdline
8250.nr_uarts=1 cma=256M bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait usbhid.mousepoll=0 coherent_pool=6M smsc95xx.turbo_mode=NBest regards, Leon
Jan-Simon Moeller December 6, 2018 at 8:39 AM
Jan-Simon Moeller
December 6, 2018 at 8:39 AM
Cma=256m
E.g. https://lava.automotivelinux.org/scheduler/job/611
This is using the build from
https://download.automotivelinux.org/AGL/upload/ci/flounder/6.0.0/raspberrypi3/deploy/images/raspberrypi3/
https://download.automotivelinux.org/AGL/upload/ci/flounder/6.0.0/raspberrypi3/deploy/images/raspberrypi3/agl-demo-platform-crosssdk-raspberrypi3-20180929155251.rootfs.ext4.xz
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@Leon Anavi , @Stephane Desneux 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.