The next step for this bug is that we need to narrow down what patch in the upstream kernel provides the fix. The best way to achieve this is via doing a git bisection search. See https://wiki.ubuntu.com/Kernel/KernelBisection.
From the comments it sounds like three things are needed:
* The mainline kernel .39
* Delete your .config/monitors.xml
* Don't arrange monitors one above the other (interesting; why? maybe unrelated bug?)
None of us X devs have arrandale HW, so progress on this bug is blocked until someone who *does* have it can do the git bisection work to narrow the patches. I asked Intel about this bug today but they didn't know offhand what patch(es) should be pulled either.
To re-emphasize what I said in comment #28:
The next step for this bug is that we need to narrow down what patch in the upstream kernel provides the fix. The best way to achieve this is via doing a git bisection search. See https:/ /wiki.ubuntu. com/Kernel/ KernelBisection.
From the comments it sounds like three things are needed:
* The mainline kernel .39 monitors. xml
* Delete your .config/
* Don't arrange monitors one above the other (interesting; why? maybe unrelated bug?)
None of us X devs have arrandale HW, so progress on this bug is blocked until someone who *does* have it can do the git bisection work to narrow the patches. I asked Intel about this bug today but they didn't know offhand what patch(es) should be pulled either.