Bug 94429

Summary: Weston dosn't start with gma500 (Poulsbo) driver
Product: Wayland Reporter: Pietro Sam <nerosamm>
Component: westonAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: blocker    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: weston launch output
Command bug multiple times but in different ways
PC SPEC
log-file1.txt
log-file2.txt
log-file05.txt
log-file33.txt
--use-pixman make serverx error
Xwayland error log

Description Pietro Sam 2016-03-07 17:01:58 UTC
Created attachment 122147 [details]
weston launch output

On arch linux (on Eee PC) with gma500 (Poulsbo) driver, when I try to start weston compositor it crash after write this string:
pci id for fd 14: 8086:0be1, driver (null)

I don't now how to solve and on web there isn't any suggestion or tips.
Comment 1 Pekka Paalanen 2016-03-08 09:47:12 UTC
I wonder if that driver is even supposed to support the EGL GBM platform.

To avoid GL and EGL problems, you could try with --use-pixman as an argument to weston.
Comment 2 Daniel Stone 2016-03-08 12:34:48 UTC
(In reply to Pekka Paalanen from comment #1)
> I wonder if that driver is even supposed to support the EGL GBM platform.
> 
> To avoid GL and EGL problems, you could try with --use-pixman as an argument
> to weston.

I wouldn't think so, but then again I've never seen a version new enough that it supported EGL_EXT_client_extensions ...

This is almost certainly a bug or missing functionality inside the EGL driver: can you please provide the log file created from running weston --log=logfile.txt?
Comment 3 Pietro Sam 2016-03-11 13:04:04 UTC
Created attachment 122222 [details]
Command bug multiple times but in different ways

Command bug multiple times but in different ways...
Number in "log-file*" are random.
(you can find the "log-file*" in other attachment)
Comment 4 Pekka Paalanen 2016-03-11 13:34:30 UTC
That attachment is definitely not text/plain. Could you fix the mime type, please?
Comment 5 Pietro Sam 2016-03-11 13:41:50 UTC
Created attachment 122224 [details]
PC SPEC

PC SPEC
Comment 6 Pietro Sam 2016-03-11 14:18:33 UTC
Created attachment 122226 [details]
log-file1.txt

122222: Command bug multiple times but in different ways
log-file1.txt
Comment 7 Pietro Sam 2016-03-11 14:21:43 UTC
Created attachment 122227 [details]
log-file2.txt

122222: Command bug multiple times but in different ways
log-file2.txt
Comment 8 Pietro Sam 2016-03-11 14:22:52 UTC
Created attachment 122228 [details]
log-file05.txt

122222: Command bug multiple times but in different ways
log-file05.txt
Comment 9 Pietro Sam 2016-03-11 14:25:18 UTC
Created attachment 122229 [details]
log-file33.txt

122222: Command bug multiple times but in different ways
log-file33.txt
Comment 10 comicfans44 2016-03-13 12:26:40 UTC
I've found weston call eglSwapBuffers and crash in kms_swrast_dri.so on GMA500

Thread 2 "llvmpipe-0" received signal SIGBUS, Bus error.
[Switching to Thread 1379.1385]
0xb755e633 in ?? ()
(gdb) up  
#1  0xb6e2960b in lp_rast_shade_tile (task=0x80a9ab4, arg=...) at lp_rast.c:352

BEGIN_JIT_CALL(state, task);
         variant->jit_function[RAST_WHOLE]( &state->jit_context,
                                            tile_x + x, tile_y + y,
                                            inputs->frontfacing,
                                            GET_A0(inputs),
                                            GET_DADX(inputs),
                                            GET_DADY(inputs),
                                            color,
                                            depth,
                                            0xffff,
                                            &task->thread_data,
                                            stride,
                                            depth_stride);
so maybe this is bug in mesa
Comment 11 Pekka Paalanen 2016-03-14 09:15:11 UTC
(In reply to comicfans44 from comment #10)
> I've found weston call eglSwapBuffers and crash in kms_swrast_dri.so on
> GMA500
...
> so maybe this is bug in mesa

Quite probably.

By the way, the only way how gma500 is involved here is that you don't have (proprietary) OpenGL drivers for it. Instead you have Mesa, which picks a software renderer, because it's all it has.

"GL renderer: Gallium 0.4 on llvmpipe" and kms_swrast_dri.so refer to software renderers in Mesa.

If you are stuck with software rendering anyway, you might as well forget OpenGL, because Weston's Pixman renderer should outperform software OpenGL any day, I believe. That's why I propose to just have --use-pixman for Weston. You can still run software-rendered GL apps with Mesa as your OpenGL implementation.

But if you really want to have kms_swrast_dri.so working, that's between you and Mesa, I think.

If --use-pixman works, there is nothing to fix in Weston.
Comment 12 comicfans44 2016-03-15 13:03:25 UTC
(In reply to Pekka Paalanen from comment #11)
> (In reply to comicfans44 from comment #10)
> > I've found weston call eglSwapBuffers and crash in kms_swrast_dri.so on
> > GMA500
> ...
> > so maybe this is bug in mesa
> 
> If you are stuck with software rendering anyway, you might as well forget
> OpenGL, because Weston's Pixman renderer should outperform software OpenGL
> any day, I believe. That's why I propose to just have --use-pixman for
> Weston. You can still run software-rendered GL apps with Mesa as your OpenGL
> implementation.
> 
I haven't found --use-pixman option, did you mean --with-cairo=image ?
Comment 13 Daniel Stone 2016-03-15 14:05:15 UTC
--use-pixman is an option to pass when running Weston, not at the configure stage.
Comment 14 Pekka Paalanen 2016-03-15 14:25:35 UTC
Ha, I see we have forgotten to document --use-pixman in 'man weston-drm', but at least 'weston --help' prints it.
Comment 15 Pietro Sam 2016-03-15 18:02:56 UTC
Created attachment 122329 [details]
--use-pixman make serverx error

With --use-pixman parameter I can't start x11 application. Solution?
Comment 16 Daniel Stone 2016-03-15 18:26:26 UTC
It seems something has gone wrong with Xwayland; what that is I can't possibly guess from a picture of the screen. But that is something which works with --use-pixman and in general (I tested), so try looking at your logs, e.g. for failing to find the Xwayland binary, or not having the xwayland.so module loaded for Weston.
Comment 17 Pietro Sam 2016-03-17 12:56:38 UTC
Created attachment 122374 [details]
Xwayland error log
Comment 18 Pekka Paalanen 2016-03-17 13:38:27 UTC
(In reply to Pietro Sam from comment #17)
> Created attachment 122374 [details]
> Xwayland error log

You have not installed Xwayland yet.

I'd be more worried about the "queueing pageflip failed" messages, though. Maybe the poulsbo driver in the kernel is... lacking.

Anyway, nothing we can do for you here about the GMA500.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.