Re: Inconsistent behaviour in guppy agl-demo-platform for bbe & raspberrypi3

["Paul Barker" <paul@xxxxxxxxxxxxxx>]

On Mon, 11 Mar 2019, at 15:03, Jan-Simon Moeller wrote:
> Could you put that in a jira and assign to the creator of the patch ?

Done!

https://jira.automotivelinux.org/browse/SPEC-2251

> Best,
> Jan-Simon
> 
> On Mon, Mar 11, 2019 at 3:45 PM Paul Barker <paul@xxxxxxxxxxxxxx> wrote:
> > I've been testing the agl-demo-platform image built from the guppy branch on both the Sancloud BBE and the Raspberry Pi 3. On both devices I'm getting inconsistent behaviour. Sometimes the system boots and works as expected. More often than not though I see one of the following failure modes:
> > 
> >  * Blank screen.
> >  * Launcher screen with top & bottom bars shows up correctly but clicking the app icons does nothing.
> >  * The launcher shows up with all icons, but no top bar or bottom bar is visible on the screen.
> >  * The top and bottom bars show up but there is no launcher in the middle. Trying to click any of the app icons in the top bar does nothing.
> > 
> >  It seems to be fairly random which failure mode I get.
> > 
> >  On the BBE the issue seems to be fixed completely be reverting commit 42dbcc0d19bc5571c3e80588139a069128551900 "Improve integration of callsync" in libwindowmanager. On the raspberrypi3 the same change does improve things, giving a working system on most boots but there are still occasional failures to a blank screen.
> > 
> >  Has anyone else seen this behaviour on raspberrypi3? Or are there any suggestions on where to go next with debugging this? The libwindowmanager commit that seems to cause most of the issues is a bit opaque to me as I don't know the details of how this component is expected to work.
> > 

-- 
Paul Barker
Managing Director & Principal Engineer
Beta Five Ltd
_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions