(In reply to comment #23)
yeah,my old conclusion is wrong.I do more detailed testing again:
I used the xserver 1.4 with latest git source code or relese version driver(intel-2.2.0) both can reproduce this bug.When I used xserver git source with latest intel git source code or release version driver(intel-2.2.0) can not reproduce this bug. So this bug is not intel dirver’s problem.Willi,You can try using the latest xserver git source code and see if this problem gone or not.
(In reply to comment #23)
yeah,my old conclusion is wrong.I do more detailed testing again:
I used the xserver 1.4 with latest git source code or relese version driver(intel-2.2.0) both can reproduce this bug.When I used xserver git source with latest intel git source code or release version driver(intel-2.2.0) can not reproduce this bug. So this bug is not intel dirver’s problem.Willi,You can try using the latest xserver git source code and see if this problem gone or not.