https://bugs.freedesktop.org/show_bug.cgi?id=63404
Priority: medium
Bug ID: 63404
Assignee: mesa-dev@lists.freedesktop.org
Summary: [wayland egl] intel_do_flush_locked failed: invalid
argument, crash
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: joe.ko...@linux.intel.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Other
Product: Mesa
When using the DRI2 EGL Wayland backend, varying circumstances will elicit the
following stderr printf, followed by a mesa crash, resulting in a black, hung
display:
intel_do_flush_locked failed: Invalid argument
It is difficult to consistently reproduce. What initially got me looking was a
usage scenario where multiple instances of a Wayland client ('gears', which
borrows heavily from 'glxgears') were being launched. It's a roll of the dice
which instance brings the issue to the fore.
So far, usage scenarios that cause this issue:
* launch multiple instances of a GL or EGL client (Weston 'gears' or
'simple-egl') in rapid succession on Weston w/ drm-backend
- on the order of gears [& gears]+
* launching the drm-backend of the Weston display manager
* launching a GLMark2 GL|ES2 benchmark using the es2-wayland backend
This regression seems to have occurred somewhere in Mesa master between commit
'8aa8b05' and '032e554'. This regression is not seen on the 9.0 branch.
Bisecting this is proving tedious, and progress slow.
If anyone would like to help with bisection, by all means.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
