Comment 22 for bug 1079440

Okay,

I've loaded up a nightly build of 3.7.0 (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/ -- the one I got was "3.7.0-994.201212210409". That didn't change things. Then I set up the xorg-edgers PPA as described in "https://launchpad.net/~xorg-edgers/+archive/ppa/+index?batch=75". [That brings in yet another 3.7.0 kernel.]

With all the new xorg software, using the current kernel or either of the 3.7.0 kernels, nothing seems to be broken that didn't used to be broken, but the problem still occurs after a few minutes.

The effect of CTL-ALT-F1 (virtual terminal) is inconsistent, so I can't rely on that to upload more details. I could probably set something up on a regular terminal that could be sent by a few simple keystrokes after the freeze occurs. I don't know what that would be, perhaps some form of appport. If someone would like me to do this, please suggest a method.

If developers would like to try to find this on their own systems, let me point out that both of the reports in launchpad bug 1079440 concern computers with the same combination of i954 chips.

My setup is simple: (1) use a terminal to run a perl-one-liner that squirts a running count to the screen, then position that on the boundary of the two displays; (2) set up a system monitor so that the activity graph is scrolling across both monitors; (3) set up an emacs editor and select its window; (4) wait a few minutes, typing into emacs as you please -- then save your scribblings after the freeze.

Let me know what more I can do to help you find this.