With latest commits to mesa, resizing a surface in weston causes the surface to disappear. gdb shows the process exited normally. Sometimes though, I am able to crash weston which leaves the single message "intel_do_flush_locked failed: Invalid argument". I bisected to find:
de315f76a266ce51ca0638b9ea2ec3ccfd31f03b is the first bad commit
Author: Kristian Høgsberg <firstname.lastname@example.org>
Date: Sat Feb 2 12:26:12 2013 -0500
wayland: Add prime fd passing as a buffer sharing mechanism
Reviewed-by: Ander Conselvan de Oliveira <email@example.com>
:040000 040000 64fd9e653501abd636b0aebcb7b6f3d046cfad88 8944e7c531c68cc90173b16bc787a457a47ef66b M src
The bug can be reproduced with:
Sandybridge, xubuntu 12.10 64bit, 3.5.0-26-generic
I cannot reproduce this issue on:
please, consider rebuilding the whole stack.
(In reply to comment #1)
> I cannot reproduce this issue on:
> wayland 7165bf21917ed1c4f5ec823a1e1642a9e83aa984
> weston 706d15e2a7048875f6ebbda529f53cf4a090b935
> mesa b101a094b5576337f5bb7aecf525eb1755757b9c
> please, consider rebuilding the whole stack.
Hi, this only happens with Intel. What hardware are you using to test there?
I can reproduce it on Intel Ivy Bridge
Sometimes wayland client dies, sometimes weston exits with output:
intel_do_flush_locked failed: No such file or directory
Intel Ivy Bridge
Linux 3.7.10-1-ARCH x86_64
I can reproduce it when the only change in software is going from mesa 9.1.1 to mesa git.
Mesa revision: 3e10ab6b22341c06a9352b1e029b923f4d8405b9
My hardware seems to be Sandybridge, but I can't tell with this lspci:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
Created attachment 76944 [details]
full backtrace of the bug
This is actually a kernel bug, introduced in kernel 3.8. It seems some distros picked up the patch that introduced the issues, hence the failures on Ubuntu with 3.5 and ARCH with 3.7. They should include also a fix for this issue. Details on the duplicate bug.
*** This bug has been marked as a duplicate of bug 63404 ***