Ubuntu
xserver-xorg-video-intel package

  1. Lucid (10.04)
  2. Bug #541492
  3. Comment #259

Comment 259 for bug 541492

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

System/hardware:
10.04 (lucid) 2.6.32-25-generic

1024x768

$ lspci|grep "VGA"
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)

This reproduces the problem consistently (gnome-screensaver is installed):

System|Preferences|Screensaver.

By default, AntSpotlight is selected. After a couple of seconds the screen goes blank, sometimes with vertical zebra stripes.

syslog contains:

Oct 2 12:26:41 ubuntu-desktop kernel: [ 5531.425838] [drm:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck
Oct 2 12:26:41 ubuntu-desktop kernel: [ 5531.740027] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Oct 2 12:26:41 ubuntu-desktop kernel: [ 5531.740038] render error detected, EIR: 0x00000000
Oct 2 12:26:41 ubuntu-desktop kernel: [ 5531.740880] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 4120 at 1135)
Oct 2 12:26:43 ubuntu-desktop kernel: [ 5533.792017] [drm:i915_gem_idle] *ERROR* hardware wedged

So after a reboot (pressing the power button seems to more-or-less cleanly shutdown), at GRUB, I've pressed 'e' to edit and after "quiet splash" I've added "i915.modetest=1" (no quotes).

After that, I can go to the screen saver preferences and there is no black screen/"crash". Screensaver comes in after the specified time and works, probably slowly, though.

However, I then realised that "modetest" should have been "modeset". So, not surprisingly,
syslog reports:

kernel: [ 18.768163] i915: Unknown parameter `modetest'

If I use modeset=0, or modeset=1, then the blanking/"crash" still happens when I go to the screensaver preferences.

So, modetest=0 or modetest=1 (either one avoids the blanking) is doing *something*. But what, and why?

Anyway, I'm happy to live with this until the official release of Maverick, which hopefully will solve things.