[i915gm] karmic 2.6.31-2 and -3 lid closing blacks screen until reboot on thinkpad r52

[Mike Jacobi]

IBM Thinkpad R52 1859 karmic upgraded from jaunty and again to latest july 15 4am est (alpha 2?)

Regardless of the power management setting for what to do on lid close (tried Blank Screen and Do Nothing), the screen stays black on lid open. It seems to come on, but it stays black. I was able to reboot with Ctrl+Alt+F1 then ctrl+alt+delete. It doesn't seem like the OS froze, just the display is black. Fine again after a reboot.

If I switch to my old jaunty .29 kernel on boot, it doesn't happen.
Could it be an issue in "DeviceKit-power" or "udev-extras"?

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
     Subsystem: IBM Device [1014:0575]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03)
     Subsystem: IBM Device [1014:0582]

[Mike Jacobi (nytimes)]

dmesg.txt attached, though I'm currently running the -29 jaunty kernel.

[Mike Jacobi (nytimes)]

lspci.txt attached

[Mike Jacobi (nytimes)]

dmesg while running affected 2.6.31-3 karmic kernel
attached

[Philip Muškovac (yofel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in xserver-xorg-video-intel.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Bryce Harrington (bryce)]

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[Mike Jacobi (nytimes)]

Attaching lspci -vvnn results.

(I've updated karmic to the latest packages. My current kernel is 2.6.31-5-generic. The bug is still there.)

[Mike Jacobi (nytimes)]

Attaching Xorg.0.log after reproducing the issue and closing/opening lid a second time (which didn't help.)

[Mike Jacobi (nytimes)]

Attaching my xorg.conf file. I don't think my customizations here are related to the bug.

[Mike Jacobi (nytimes)]

I found a new workaround to make the screen come back on. Fn + F7 (toggles between laptop LCD, External VGA, and both mirrored.) Pressing this combination turned my laptop LCD back on. I'm 99% certain this workaround did not work when I first reported this bug running earlier karmic packages.

[Bryce Harrington (bryce)]

Hi Mike,

I'm not sure if its the same issue or not, but "blanks on lid close" sounds similar to a certain class of bugs we can do quirk fixes for. Can you refer to this page about PipeA settings, and test that out to see if it resolves the problem? If so, include the info that is described there and I can request a quirk patch for it.

https://wiki.ubuntu.com/X/Quirks#Force%20Pipe%20A%20Quirk

[Mike Jacobi (nytimes)]

This didn't do the trick. Still have to press Fn + F7 to get my screen back from completely black (it's on, but black).

[Manuel Siggen (manuel-siggen)]

Hello, the problem seems similar to the one described in Bug 417599, for what it's worth...

[Igor Gomes (igorgomes)]

Could it be related with Bug 431812?

Igor Gomes

[Mike Jacobi (nytimes)]

I cannot reproduce Bug 417599 and I don't believe I've ever seen Bug 431812 happen.

I tried to reproduce my bug again and I could not recover this time with Fn-F7 (crt/lcd switch). I also could not recover through switching through ttys. I think the difference may be I switched to the xfce4 window manager.

So I tried again with Gnome this time on a new user account (this one created after upgrading from jaunty to karmic).

Results:
Bug still occurs.
Fn-F7 recovers the first time, though now the screen flashes for a second before showing the desktop.
If I test it again during the same session, the screen will flash indefinitely, though I can still recover from this state by switching TTYs (ctrl-alt-F1, alt-F8).
See below for a tail of my dmesg after the two flashing states described above.
While writing this up after the above tests my system froze up (only the mouse moved, didn't check if I could ssh in). Not sure if this is related but I pasted xorg's log and the syslog, right before the freeze, below too.

dmesg after black screen recovery:
[ 876.164450] [drm] DAC-6: set mode 640x480 0
[ 876.270259] [drm] DAC-6: set mode 640x480 0
[ 876.339628] i2c-adapter i2c-1: unable to read EDID block.
[ 876.339632] i915 0000:00:02.0: LVDS-1: no EDID data
[ 876.381047] [drm] TV-12: set mode NTSC 480i 0
[ 876.521167] [drm] TV-12: set mode NTSC 480i 0
[ 876.977168] [drm] LVDS-8: set mode 19
// recovered gui here
[ 898.210123] [drm] DAC-6: set mode 640x480 0
[ 898.315048] [drm] DAC-6: set mode 640x480 0
[ 898.384402] i2c-adapter i2c-1: unable to read EDID block.
[ 898.384406] i915 0000:00:02.0: LVDS-1: no EDID data
[ 898.425775] [drm] TV-12: set mode NTSC 480i 0
[ 898.565927] [drm] TV-12: set mode NTSC 480i 0
[ 901.593519] [drm] LVDS-8: set mode 1024x768 16
[ 905.916108] [drm] LVDS-8: set mode 1a
// recovered gui here

tail of Xorg.1.log after reboot after freeze:
(II) intel(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (37.9 kHz)
(II) intel(0): EDID for output TV1
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) UnloadModule: "synaptics"
(II) TPPS/2 IBM TrackPoint: Close
(II) UnloadModule: "evdev"
(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) ThinkPad Extra Buttons: Close
(II) UnloadModule: "evdev"
(II) Sleep Button: Close
(II) UnloadModule: "evdev"
(II) Video Bus: Close
(II) UnloadModule: "evdev"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
 ddxSigGiveUp: Closing log

syslog before and after reboot:
Oct 1 01:39:24 happybox kernel: [ 1532.205968] i2c-adapter i2c-1: unable to read EDID block.
Oct 1 01:39:24 happybox kernel: [ 1532.205972] i915 0000:00:02.0: LVDS-1: no EDID data
Oct 1 01:39:24 happybox kernel: [ 1532.247359] [drm] TV-12: set mode NTSC 480i 0
Oct 1 01:39:27 happybox kernel: [ 1532.387534] [drm] TV-12: set mode NTSC 480i 0
Oct 1 01:39:27 happybox kernel: [ 1534.594420] [drm] DAC-6: set mode 640x480 0
Oct 1 01:39:27 happybox kernel: [ 1534.702300] [drm] DAC-6: set mode 640x480 0
Oct 1 01:39:27 happybox kernel: [ 1534.773173] i2c-adapter i2c-1: unable to read EDID bl...

[Mike Jacobi (nytimes)]

another update after upgrading and testing today:
xserver-xorg-video-intel Version: 2:2.9.0-1ubuntu1
Linux 2.6.31-12-generic #41-Ubuntu SMP

The bug still occurs. Fn+F7 (LCD/CRT switch combo) is back to being a quick fix; I get the screen back if I hit it once or twice (usually once).

[Zsolt Fabok (fabokzs)]

Hi,

I have exactly the same problem on my dell inspiron 6400.

I'm running a karmic-beta, upgraded yesterday from jaunty.
kernel version: 2.6.31-14-generic
xserver-xorg-video-intel version: 2:2.9.0-1ubuntu2

Xorg.log, xorg.conf and lspci output attached.

After putting the machine into stand-by state and waking it up, the lcd is visible again.

Please tell me if you need more info.

Thanks,
Zsolt

[Zsolt Fabok (fabokzs)]

It works for me now, nice job

[Zsolt Fabok (fabokzs)]

I tested this again and again, and still wrong. Sorry for the previous fast response

[saran (sarannmr)]

Hi,
    I think my computer has the same bug. (??). Atleast the symptoms are the same. After lid closes, the screen blanks out and I need to restart. ( Doesn't happen all the time....but sometimes. ). I am running on a Dell Inspiron 6400.
#uname -a
Linux ness 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

Nov 6 02:10:54 ness kernel: [ 4444.385150] integrated sync not supported
Nov 6 02:10:55 ness kernel: [ 4444.427334] [drm] TV-14: set mode NTSC 480i 0
Nov 6 02:10:55 ness kernel: [ 4444.568555] [drm] TV-14: set mode NTSC 480i 0
Nov 6 02:10:55 ness kernel: [ 4445.045432] integrated sync not supported
Nov 6 02:10:55 ness kernel: [ 4445.087375] [drm] TV-14: set mode NTSC 480i 0
Nov 6 02:10:55 ness kernel: [ 4445.228691] [drm] TV-14: set mode NTSC 480i 0
...( LOTS of these )
Nov 6 02:14:51 ness kernel: [ 4680.616108] i915/0 D c08145c0 0 308 2 0x00000000
Nov 6 02:14:51 ness kernel: [ 4680.616121] ef04bf04 00000046 ef0acb8c c08145c0 ef0acdf8 c08145c0 229f9cb4 0000040b
Nov 6 02:14:51 ness kernel: [ 4680.616140] c08145c0 c08145c0 ef0acdf8 c08145c0 229f910d 0000040b c08145c0 f68936c0
Nov 6 02:14:51 ness kernel: [ 4680.616157] ef0acb60 ef44ac14 ef44ac18 ffffffff ef04bf30 c056f776 c0748e80 ef44ac1c
Nov 6 02:14:51 ness kernel: [ 4680.616175] Call Trace:
Nov 6 02:14:51 ness kernel: [ 4680.616193] [<c056f776>] __mutex_lock_slowpath+0xc6/0x130
Nov 6 02:14:51 ness kernel: [ 4680.616203] [<c056f690>] mutex_lock+0x20/0x40
Nov 6 02:14:51 ness kernel: [ 4680.616254] [<f814ac0a>] i915_gem_retire_work_handler+0x2a/0x70 [i915]
Nov 6 02:14:51 ness kernel: [ 4680.616267] [<c0157a7e>] run_workqueue+0x6e/0x140
Nov 6 02:14:51 ness kernel: [ 4680.616306] [<f814abe0>] ? i915_gem_retire_work_handler+0x0/0x70 [i915]
Nov 6 02:14:51 ness kernel: [ 4680.616317] [<c0157bd8>] worker_thread+0x88/0xe0
Nov 6 02:14:51 ness kernel: [ 4680.616327] [<c015c280>] ? autoremove_wake_function+0x0/0x40
Nov 6 02:14:51 ness kernel: [ 4680.616338] [<c0157b50>] ? worker_thread+0x0/0xe0
Nov 6 02:14:51 ness kernel: [ 4680.616346] [<c015bf8c>] kthread+0x7c/0x90
Nov 6 02:14:51 ness kernel: [ 4680.616355] [<c015bf10>] ? kthread+0x0/0x90
Nov 6 02:14:51 ness kernel: [ 4680.616365] [<c0104007>] kernel_thread_helper+0x7/0x10
Nov 6 02:14:51 ness kernel: [ 4680.616411] compiz.real D c08145c0 0 2149 2089 0x00000000
Nov 6 02:14:51 ness kernel: [ 4680.616422] f5061e20 00200086 c050c974 c08145c0 f6938298 c08145c0 76d2c646 0000040d
Nov 6 02:14:51 ness kernel: [ 4680.616440] c08145c0 c08145c0 f6938298 c08145c0 76d0c1b1 0000040d c08145c0 ef3d4e00
Nov 6 02:14:51 ness kernel: [ 4680.616457] f6938000 ef44ac14 ef44ac18 ffffffff f5061e4c c056f776 00000000 ef44ac1c
Nov 6 02:14:51 ness kernel: [ 4680.616475] Call Trace:
Nov 6 02:14:51 ness kernel: [ 4680.616485] [<c050c974>] ? unix_stream_recvmsg+0x1d4/0x440
Nov 6 02:14:51 ness kernel: [ 4680.616496] [<c056f776>] __mutex_lock_slowpath+0xc6/0x130
Nov 6 02:14:51 ness kernel: [ 4680.616505] [<c056f690>] mutex_lock+0x20/0x40
Nov 6 02:14:51 ness kernel: [ 4680.616546] [<f814bc46>] i915_gem_set_domain_ioctl+0x86/0x110 [i915]
Nov 6 02:14:51 ness kernel: [ 4680.616595...

[saran (sarannmr)]

Let me know if this is the same...( and you want more info).

[Aviv Ben-Yosef (aviv-by)]

I've got Karmic installed on an X200s thinkpad and I'm getting the exact same call trace as saran does.
Happened to me today after locking the computer (no lid closing) and leaving it for ~30 minutes.

[Zsolt Fabok (fabokzs)]

I have a workaround, use it with precaution:

1. sudo bash
1.1 apt-get install vbetool
2. cd /etc/acpi
3. mv lid.sh lid.sh.orig
4. cat > lid.sh.new

  #!/bin/bash
  if [ ! "$(cat /proc/acpi/button/lid/LID/state | grep open)" = "" ]; then
    vbetool dpms on
  fi

5. ln -s lid.sh.new lid.sh

In nutshell, replace the current lid.sh with the snippet above (it comes from gentoo as far as I remember). Note that this step may harm your computer; if a new ubuntu supported lid.sh is installed by system manager, some unseen problem can occur

[Maarten Wisse (wisseaanen)]

I can confirm this bug for a Dell Latitude D620 with an GMA 950 Intel chip. However, on this machine, the trick with Fn-F8 does not work. Reboot or putting the machine to sleep with Fn-Esc and then power it up, fires up the screen again.

[Bart Staal (bart.staal)]

Idem dito. Dell Inspiron 6400, screen stays off (black) after closing and openening the lid, regardless of power management settings. Screen is restored after a suspend-to-ram/resume cycle.

[Alexey Alexandrov (swined)]

same things on eee pc 1005ha with kubuntu lucid (2.6.32-4-generic). sometimes (looks like absolute random) the screen gets filled with one color (usually black, but can be any other). the system is still functional, but the display is useless. can be cured by any type of power cycle. i use sleep/wake as the fastest. also the screen sometimes flickers. enabling/disabling compositing or changing any other video settings does not matter.

[Lennart Fridén (information-devl)]

This also happens (well, I don't even have to close the lid) on my ASUS EEE S101 running 10.04 with the latest updates. Sleeping or restarting restores the display.

[Jon Skanes (jon-skanes)]

This happens for me on a Dell D420. Changing the acpi lid.sh, as noted above, fixes the problem for me. Also, I tried the pipe quirk setting in my xorg.conf, but it only resulted in a bad display.

[Jon Skanes (jon-skanes)]

Here's my Xorg.0.log

[tribble222 (tribble222)]

I'm experiencing this same problem. If I suspend either by closing the lid or by choosing suspend from the menu then upon resume the screen will flicker occasionally and eventually will fill with a solid color, usually black. The system remains completely responsive but the screen won't update. Restarting gdm doesn't fix this. Switching between consoles and back doesn't work.

This is on an EEE PC 1005HA running Karmic 9.10 with kernel 2.6.32-020632.

[tribble222 (tribble222)]

Here is my dmesg after a suspend-resume-screenblank-suspend-resume.

[Andrew Kachaniwsky (kachaniwsky)]

I'm having the same issue on a Dell Latitude D620. Nothing I've tried seems to bring the screen back short of a stand-by or a full reboot.

Unfortunately I don't see an option in the BIOS to disable the screen-blanking. I have gone through gconf-editor to set the "close lid" behavior to "do nothing", but still the screen blanks.. so I have a feeling it's more a hardware thing with Dells and less a software thing. Hoping that somebody out there can come out with a solution.. it's relatively embarassing taking my laptop into a meeting and opening up the lid only to have to reboot the laptop before I can do anything useful.

[C Pirnat (histoplasmosis)]

This behavior just started for me in Lucid with recent updates on my dell inspiron 6000. I've noticed that if I tell the laptop to suspend via the power menu the system operates as normal. But if I close the lid the screen blanks the laptop doesn't go in to suspend and there is no way to wake the screen back up. I have to hard reset.

[C Pirnat (histoplasmosis)]

Now in Lucid this is happening on my new laptop with nvidia drivers. So I'm at a loss I don't think its a intel thing. I think it has to do with gnome power manager or whatever is supposed to turn the monitor back on.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Thanks for reporting this bug to help making the Intel graphics driver
better. We hear from upstream that a number of bugs (possibly including
this one) have been fixed in the newer DRM code from the 2.6.33 kernel.
I don't know if your bug is one of the ones fixed in this release,
though, but we've prepared a PPA with this DRM update. Would you mind
installing this, rebooting, and testing if the original issue can be
reproduced with it or not?

The DRM PPA is here:

    https://edge.launchpad.net/~apw/+archive/red

Note there could be new bugs... please file these as new reports using
the command 'ubuntu-bug linux' (for kernel or DRM or KMS bugs) or
'ubuntu-bug xorg' if you suspect them to be X.org issues.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Mike Jacobi (nytimes)]

I've retested in Lucid. My display now reappears after opening my laptop screen.

However, the mouse pointer is not visible though I can still click on things.

As before, pressing Fn+F7 (LCD/CRT toggle) fixes things and my mouse cursor reappears. This time I only press it once and the cursor appears (and it seems like the top and bottom gnome panels quickly refresh/flash).

Switching to a text mode tty and then back to X also gets my mouse cursor to reappear.

Just as a reminder, my laptop is configured in Ubuntu not to sleep on lid close.

I upgraded to Lucid beta1 a while ago and have the latest apt updates. My kernel is Linux 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux.

It's been a while since I last looked at this..should I still try testing the suggestion in #34?

[Chris Halse Rogers (raof)]

The “screen doesn't come back from blank when opening the lid” part of this bug has should have been fixed by the 2.6.32-19 kernel. I'm marking this bug as fixed, since you've indicated that this particular problem is fixed.

Although it's got a similar trigger, the “no cursor after opening the lid” will be a separate problem. Could you please file a new bug about that? It'll be much easier to keep track of the problem as a separate bug.