Comment 60 for bug 745608

(Subscribing dpsenner to this bug)

Dominik:
It's cool when you find a bug report that might help you fix a problem isn't it? :-)

Speaking as a random person on the Internet (I don't work for Canonical, Intel etc), it's very unlikely that you can have a bug's priority raised by asking (although subscribing/marking a bug as also affecting you is useful as it makes it clear how many people are interested in a given bug). The general reason is that while the bug may be massively disruptive for you, there are finite resources to go into fixing problems. If more people are seeing another issue just as major or more significant in some manner, then it is likely the resources will be put into solving that issue.

Of course, I would like to see this particular bug resolved too :). If this turns out to be your issue (your card's id looks the same as others that see this issue so chances are high), you can read further discussion in the upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=36326 .

To answer Ferry's question about why the fix works: one of the Intel developers mentioned that this era of graphics cards have constraints related to tiling and DebugWait disabled tiling entirely (but another issue meant that "Tiling" "false" did not disable tiling(!)). It was only in later versions of the X drivers that tiling was actually used tiling, so that's why users with old Xorgs don't see this issue.