weston-launch failed to start up in system initialize phase.

Pekka Paalanen ppaalanen at gmail.com
Thu Sep 25 23:26:30 PDT 2014


On Wed, 24 Sep 2014 06:05:17 +0000
Yang Andy <williamyang13 at hotmail.com> wrote:

> Hi everyone
> 
> I have a question about weston-launch start up in system initialize phase.
> 
> When i start up target device,weston-launch which is launch from systemd/service is crashed  in system initialize phase.
> 
> But i can run weston-launch correctly when i launch weston-launch from console terminal.
> 
> As below coredump show,it seems that eglGetDisplay has something wrong.
> 
> Could anyone give me some advice?
> 
> Best regards.
> 
> [coredump]
> Core was generated by `/usr/bin/weston -i0'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x76d67cf0 in gcoHAL_QueryChipCount (Hal=Hal at entry=0x0, Count=Count at entry=0x1dea98c) at gc_hal_user_query.c:1002
> 1002    gc_hal_user_query.c: No such file or directory.
> (gdb) where
> #0  0x76d67cf0 in gcoHAL_QueryChipCount (Hal=Hal at entry=0x0, Count=Count at entry=0x1dea98c) at gc_hal_user_query.c:1002
> #1  0x76e47a90 in veglGetThreadData () at gc_egl.c:239
> #2  0x76e3e640 in eglGetDisplay (display_id=0x1dea3f0) at gc_egl_init.c:521
> #3 
>  0x76954b5e in gl_renderer_create (ec=0x1de8fd8, display=<optimized 
> out>, attribs=0x76957414 <gl_renderer_opaque_attribs>, 
> visual_id=0x0) at src/gl-renderer.c:1936
> #4  0x769d9b00 in 
> fbdev_compositor_create (param=0x7ef936dc, config=0x1de6a08, 
> argv=<optimized out>, argc=<optimized out>, 
> display=0x1de64b0)
>     at src/compositor-fbdev.c:945
> #5  
> backend_init (display=0x1de64b0, argc=<optimized out>, 
> argv=<optimized out>, config=0x1de6a08) at 
> src/compositor-fbdev.c:998
> #6  0x0000e6ee in main (argc=1, argv=0x7ef93b24) at src/compositor.c:4240

Hi,

it looks like you are using a properietary graphics stack. We at weston
upstream cannot help you with that, because I assume the source code is
not public.

A wild guess: could it be that your system loads some graphics
(kernel?) drivers in parallel, and when weston is first attempted, the
driver has not loaded yet?


Thanks,
pq


More information about the wayland-devel mailing list