On Tue, 14 Jan 2014 10:26:15 +0100 albert <[email protected]> wrote: > Thanks for the info Pekka, > > Attached are weston-launch and xserver log files. df -h tells > me /run/shm has 75MB of free space. The crash is almost inmediate, I > would think xf-86-video-wayland delegates control at this point: > > http://cgit.freedesktop.org/xorg/driver/xf86-video-wayland/tree/src/wayland.c#n497 > > And this is how I autogen the xserver - wayland branch: > > ./autogen.sh --disable-glx --disable-dri > '--disable-dri2 --disable-dri3 --disable-libunwind > '--disable-devel-docs --disable-docs > --disable-dependency-tracking > '--disable-glx --disable-xinerama --disable-composite > --disable-record > '--disable-present --disable-screensaver --prefix=$WLD
Ok, thanks. There is one thing that looks strange to me in your X log: [ 6208.872] (II) Loading /root/weston-bin/lib/xorg/modules/drivers/wayland_drv.so [ 6208.874] (II) Module wayland: vendor="X.Org Foundation" [ 6208.874] compiled for 1.12.4, module version = 0.4.0 [ 6208.874] Module class: X.Org Video Driver [ 6208.874] ABI class: X.Org Video Driver, version 15.0 while e.g. the xwayland xserver module says "compiled for 1.15.0". Could you somehow have compiled the wayland ddx against the distro xserver which is 1.12.x? Could you check if you rebuild xf86-video-wayland and get it to say "compiled for 1.15.0" whether that fixes it? I wonder if xf86-video-wayland is missing an ABI check, maybe towards xwayland module? Thanks, pq > 2014/1/14 Pekka Paalanen <[email protected]> > > > On Tue, 14 Jan 2014 09:07:31 +0100 > > albert <[email protected]> wrote: > > > > > Greetings all, > > > > > > I am trying to make XWayland run on a Raspberry PI, so I am > > > building wayland/weston and the xserver xwayland branch from here: > > > > > > git://anongit.freedesktop.org/xorg/xserver > > > > > > As well as the wlshm (now moved as wayland) driver: git:// > > > anongit.freedesktop.org/xorg/driver/xf86-video-wayland > > > > > > When attempting to start a x11 app, the xserver effectively is > > > started, the wayland x driver loads successfully but when > > > attempting to "subload" the framebuffer driver, it segfaults. > > > This fb driver has been built as part of this same xserver. > > > > > > [ 1056.806] (II) Loading sub module "fb" > > > [ 1056.806] (II) LoadModule: "fb" > > > [ 1056.808] (II) > > > Loading /root/weston-bin/lib/xorg/modules/libfb.so [ 1056.811] > > > (II) Module fb: vendor="X.Org Foundation" [ 1056.811] > > > compiled for 1.15.0, module version = 1.0.0 [ 1056.812] ABI > > > class: X.Org ANSI C Emulation, version 0.4 [ 1056.812] (==) > > > Depth 24 pixmap format is 32 bpp [ 1056.813] (==) wayland(0): > > > Backing store disabled [ 1056.813] (==) wayland(0): Silken mouse > > > enabled [ 1056.815] (EE) > > > [ 1056.815] (EE) Backtrace: > > > [ 1056.815] (EE) > > > [ 1056.816] (EE) Segmentation fault at address 0xe7933016 > > > [ 1056.816] (EE) > > > Fatal server error: > > > [ 1056.816] (EE) Caught signal 11 (Segmentation fault). Server > > > aborting > > > > > > The contents of the xorg.conf file looks like so: > > > > > > Section "Device" > > > Identifier "Device" > > > Driver "wayland" > > > EndSection > > > > > > Any hints on what I might be missing would be greatly > > > appreciated, or even hints on how to debug this fault, as there > > > is no timeframe to gdb attach against the xserver before it dies. > > > > Hi Albert, > > > > that does not ring any bells for me. Could you attach the output of > > weston-launch (both stdout and stderr together), and the whole X > > log. Also check the free space in your XDG_RUNTIME_DIR, though I'd > > assume running out of space would cause SIGBUS rather than SEGV. > > > > I don't recall off-hand how to run the xwayland xserver under gdb, > > maybe someone else does? Might involve a bit of hacking. > > > > > > Thanks, > > pq > > _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
