I see the artifacts due to Taskbar using ResolverActivity which is using gralloc flag SW_WRITE_OFTEN for buffers that need CPU write,
but Skylake GT1 (iris) is the first Intel platform affected by the problem. Infact on a Baytrail (crocus) the GUI is rock stable and there are no ResolverActivity artifacts.
I guess that this time I can open an issue to mesa, because i965 and crocus do not have such problems and they will triage if the problem is in gbm_gralloc or in mesa gbm/dri backend.
You may also notice the disrupted cursor near the center of Navigation bar, those cursor artifacts do not depend on ResolverActivty, that is an independent additional problem, which extremely weird because gbm_gralloc does not even pass the cursor flag to mesa gbm at buffer allocation.
Due to continuos GUI crashes, in order to be able to get the tombstones I had to connect via Ethernet cable with static IP address.
I believe the tombstones where system_server crashes the one correlated to GUI restarts (not attaching them based on the assumption that the problem is related to ResolverActivity window (the one garbled)
If passed that step of launcher selection there is no GUI crash, then the attached patch for framework/base project should also allow to to see the ResolverActivity window to choose the launcher.