intel drm GPU hang on every boot (before GDM) after installing lucid updates

Bug #507590 reported by Martin Olsson
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
X.Org X server
Invalid
Medium
xorg (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

I've had lucid on this machine for weeks and it's been very stable. After installing updates and rebooting it now won't boot. Instead of GDM I get a black screen (with a single row of multicolored pixels near the top of the screen). I hear the Ubuntu drum sound when it arrives at the GDM screen and I can login via ssh. In dmesg/xorglog I see GPU hang errors.

ProblemType: Bug
Architecture: amd64
Date: Thu Jan 14 19:24:05 2010
DistroRelease: Ubuntu 10.04
MachineType: Gigabyte Technology Co., Ltd. EG45M-DS2H
Package: xorg 1:7.5+1ubuntu1
ProcCmdLine: root=UUID=72c40d5f-31c8-4ab1-886d-8b266543b5c6 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
RelatedPackageVersions:
 xserver-xorg 1:7.5+1ubuntu1
 libgl1-mesa-glx 7.7-0ubuntu4
 libdrm2 2.4.17-0ubuntu1
 xserver-xorg-video-intel 2:2.9.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20091125.0061c4db-0ubuntu2
SourcePackage: xorg
Symptom: display
Tags: freeze lucid
Title: Xorg freeze
Uname: Linux 2.6.32-10-generic x86_64
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
dmi.bios.date: 07/18/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: EG45M-DS2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/18/2008:svnGigabyteTechnologyCo.,Ltd.:pnEG45M-DS2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG45M-DS2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EG45M-DS2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
fglrx: Not loaded
glxinfo: Error: command ['glxinfo'] failed with exit code 255: Error: unable to open display
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.32-10-generic
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

Revision history for this message
In , Martin Olsson (mnemo) wrote :

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

Revision history for this message
In , Martin Olsson (mnemo) wrote :
Revision history for this message
In , Martin Olsson (mnemo) wrote :

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.

Revision history for this message
Martin Olsson (mnemo) wrote :

Binary package hint: xorg

I've had lucid on this machine for weeks and it's been very stable. After installing updates and rebooting it now won't boot. Instead of GDM I get a black screen (with a single row of multicolored pixels near the top of the screen). I hear the Ubuntu drum sound when it arrives at the GDM screen and I can login via ssh. In dmesg/xorglog I see GPU hang errors.

ProblemType: Bug
Architecture: amd64
Date: Thu Jan 14 19:24:05 2010
DistroRelease: Ubuntu 10.04
MachineType: Gigabyte Technology Co., Ltd. EG45M-DS2H
Package: xorg 1:7.5+1ubuntu1
ProcCmdLine: root=UUID=72c40d5f-31c8-4ab1-886d-8b266543b5c6 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
RelatedPackageVersions:
 xserver-xorg 1:7.5+1ubuntu1
 libgl1-mesa-glx 7.7-0ubuntu4
 libdrm2 2.4.17-0ubuntu1
 xserver-xorg-video-intel 2:2.9.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20091125.0061c4db-0ubuntu2
SourcePackage: xorg
Symptom: display
Tags: freeze lucid
Title: Xorg freeze
Uname: Linux 2.6.32-10-generic x86_64
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
dmi.bios.date: 07/18/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: EG45M-DS2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/18/2008:svnGigabyteTechnologyCo.,Ltd.:pnEG45M-DS2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG45M-DS2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EG45M-DS2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
fglrx: Not loaded
glxinfo: Error: command ['glxinfo'] failed with exit code 255: Error: unable to open display
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.32-10-generic
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

Revision history for this message
Martin Olsson (mnemo) wrote :
Revision history for this message
Martin Olsson (mnemo) wrote :

DMESG ends with:
[ 17.200905] ppdev: user-space parallel port driver
[ 20.112888] 4:2:1: cannot get freq at ep 0x84
[ 20.230511] 4:2:1: cannot get freq at ep 0x84
[ 22.260025] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
[ 22.260034] render error detected, EIR: 0x00000000
[ 22.260036] i915: Waking up sleeping processes
[ 22.260050] [drm:i915_wait_request] *ERROR* i915_wait_request returns -5 (awaiting 13 at 12)
[ 22.260276] [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
[ 27.304474] eth0: no IPv6 routers present

xorg log and .0.log both contain this:
Fatal server error:
Failed to submit batchbuffer: Input/output error
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Revision history for this message
Martin Olsson (mnemo) wrote :
Revision history for this message
Martin Olsson (mnemo) wrote :

I forwarded the batch buffer dump upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=26046

Revision history for this message
Martin Olsson (mnemo) wrote :

Via the GRUB "recovery" menu I was able to select "Repair packages" ... and that ran apt-get dist-upgrade which in turn installed mesa 7.7-0ubuntu5 and now my machine boot just fine again.

Changed in xorg (Ubuntu):
status: New → Fix Released
Changed in xorg-server:
status: Unknown → Invalid
Revision history for this message
Melvin Garcia (virtualspectre8) wrote :

I have a similar problem. I get the Ubuntu logo and the cursor as if it was busy, sometimes I hear the drums, other times not. I have to got to run level 1, then alt-ctrl-f7 to see the gdm, when I select my name and type the password, it hangs, so I have to repeat run level 1 and alt-ctrl-f7 to see the desktop boot.

Changed in xorg-server:
importance: Unknown → Medium
Changed in xorg-server:
importance: Medium → Unknown
Changed in xorg-server:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.