Comment 27 for bug 541492

Revision history for this message
pakraticus (pakraticus) wrote : Re: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)

Chris Rogers,
The following is my current kludge around. An xorg.conf only containing.

Section "Device"
  Identifier "my-self-configured-device"
  Driver "intel"
 Option "DRI" "Off"
EndSection

GL apps still work, but are painfully slow, but it beats not working at all. The above kludge was actually derived from the troubleshooting documentation.

At this point in time I am seeing the system crash/lock to the affected system is no longer on the network

00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
 Subsystem: IBM Device 0267
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at 88000000 (32-bit, prefetchable) [size=128M]
 Memory at 80000000 (32-bit, non-prefetchable) [size=512K]
 Capabilities: <access denied>
 Kernel modules: i915

With i915.modeset=0 added to the kernel command line I keep seeing white vertical bars flash across the top half-third of the screen and iterations of
[ 167.472853] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 1770 at 1733)
[ 169.524015] [drm:i915_gem_idle] *ERROR* hardware wedged
[ 170.647918] [drm:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck
[ 171.008012] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
[ 171.008023] render error detected, EIR: 0x00000000

in dmesg. And the machine stays on the network with the extra parameter.

The problem happens with both 2:2.9.1-3ubuntu2~gomyhr1~clipsolids and 2:2.9.1-3ubuntu1 on 2.6.32-19-generic.

If someone wouldn't mind reminding me how to setup a serial console for debugging this kind of annoyance I'll gladly collect as much debug information as upstream wants.

My two cents of things to do before Lucid ships are
1) Prominently include in the release notes that xserver-xorg-video-intel is broken.
2) Prominently include in the release notes the work around xorg.conf.
3) Repeat #1 and #2 in a recognizeably named file in /usr/share/doc/xserver-xorg-video-intel along with this bug tracking number and upstream's bug tracking number.

If someone is feeling very creative, try having the crash hooks install that stub xorg.conf and reboot the system.