KeithM, there is no reason to stay with the red PPA anymore, since the updates from there now has made it into the standard Lucid kernel 2.6.32-16. I think we have tried the different options that we have here and need to take this upstream. In order to give them the most up-to-date information to the intel developers it would be nice if you could reproduce with the newest drm-intel-next kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ booted with the kernel option drm.debug=0x02 (after quiet splash), ssh in from another computer and grab /sys/kernel/debug/dri/0/i915_error_state, /var/log/Xorg.0.log, and the output of dmesg (which will have more information than usual, due to the drm.debug=0x02 option).
The automatic reporting script /usr/share/apport/apport-gpu-error-intel.py should run better now than before, but for now this manual procedure would be best.
KeithM, there is no reason to stay with the red PPA anymore, since the updates from there now has made it into the standard Lucid kernel 2.6.32-16. I think we have tried the different options that we have here and need to take this upstream. In order to give them the most up-to-date information to the intel developers it would be nice if you could reproduce with the newest drm-intel-next kernel from http:// kernel. ubuntu. com/~kernel- ppa/mainline/ drm-intel- next/ booted with the kernel option drm.debug=0x02 (after quiet splash), ssh in from another computer and grab /sys/kernel/ debug/dri/ 0/i915_ error_state, /var/log/ Xorg.0. log, and the output of dmesg (which will have more information than usual, due to the drm.debug=0x02 option).
The automatic reporting script /usr/share/ apport/ apport- gpu-error- intel.py should run better now than before, but for now this manual procedure would be best.