Created attachment 32640 [details] dri_debug.tgz My Ubuntu lucid machine stopped booting recently. Instead of GDM I get a black screen with a horizontal multicolor 1 pixel line near the top of the screen. I hear the Ubuntu drum sound when it arrives at GDM though. I can login to the machine via SSH and I found a "GPU hung" error in dmesg. I captured batch buffers while hung (see attachment).
Happens using 2.6.32-10-generic lucid kernel (AMD64) and these package versions: xserver-xorg-core 2:1.7.3.902-1ubuntu5 xserver-xorg-core-dbg 2:1.7.3.902-1ubuntu5 intel-gpu-tools 1.0.2-1 libdrm-intel1 2.4.17-0ubuntu1 xserver-xorg-video-intel 2:2.9.1-1ubuntu1 xserver-xorg-video-intel-dbg 2:2.9.1-1ubuntu1 libgl1-mesa-dev 7.7-0ubuntu4 libgl1-mesa-dri 7.7-0ubuntu4 libgl1-mesa-glx 7.7-0ubuntu4 libglu1-mesa 7.7-0ubuntu4 libglu1-mesa-dev 7.7-0ubuntu4 libosmesa6 7.7-0ubuntu4 mesa-common-dev 7.7-0ubuntu4 mesa-utils 7.7-0ubuntu4 libdrm-dev 2.4.17-0ubuntu1 libdrm-intel1 2.4.17-0ubuntu1 libdrm-nouveau1 2.4.17-0ubuntu1 libdrm-radeon1 2.4.17-0ubuntu1 libdrm2 2.4.17-0ubuntu1 compiz 1:0.8.4-0ubuntu10 compiz-core 1:0.8.4-0ubuntu10 compiz-fusion-plugins-extra 0.8.4-0ubuntu2 compiz-fusion-plugins-main 0.8.4-0ubuntu1 compiz-gnome 1:0.8.4-0ubuntu10 compiz-plugins 1:0.8.4-0ubuntu10 compizconfig-backend-gconf 0.8.4-0ubuntu1 compizconfig-settings-manager 0.8.2-0ubuntu1 libcompizconfig0 0.8.4-0ubuntu1 python-compizconfig 0.8.2-0ubuntu1
Downstream bug is here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/507590
Via the Ubuntu GRUB "Recovery" option I was able to run an apt-get dist-upgrade from non-GUI mode and that installed a newer version of mesa (7.7-0ubuntu5) and that fixed my computer. I suppose one of the Ubuntu packagers also ran into this bug right after mesa 7.7-0ubuntu4 was uploaded and therefore uploaded 7.7-0ubuntu5 shortly after containing the fix. The attached batch buffer might still be interesting for you guys? I'm resolving the bug though.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.