Comment 64 for bug 379157

Thank you. The two logs are about as equal as they can be. The only lines that differ are the timestamp and one memory address in the backtrace. Although you don't write it explicitly, I assume that after the reboot, the ubuntu2gomyhr version performed just the same as the ubuntu0sarvatt version. I see you haven't reported this upstream, so I'll do it in a minute.

The driver version in karmic alpha-2 is 2.7.99.1 and I think this is actually a little bit older than the one you have been testing (2.7.99 from early June). The main difference in Karmic is that it also has a newer linux kernel, and for some tasks that the kernel handles (typically accelerated stuff) the fix may actually be in the kernel. Actually, after alpha-2 was released kernel mode setting has been enabled in the newer Karmic. This means that the code responsible for detecting monitors is moved to the kernel (but it is ported from the -intel driver so this bug is probably present both places). If they find the underlying problem upstream, they can probably fix it in both places, but it would be nice if you could verify that after a fix is released.