screen brightness won't come back when I open the lid

Bug #488328 reported by Nicolò Chieffo on 2009-11-25
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fix Released
linux (Ubuntu)

Bug Description

This problem happens when I close the laptop lid (in Lucid) and then open it: the screen remains completely black until I repetely hit CTRL-ALT-F1 CTRL-ALT-F7 ...
Then the screen is restored and works well.
This is in my .xsession-errors

../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 2 (00000040 00000000): Input/output error .
../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 150 (00000040 00000000): Input/output error .
../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 1 (00000040 00000000): Input/output error .
../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 2 (00000040 00000000): Input/output error .
../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 150 (00000040 00000000): Input/output error .
../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 1 (00000040 00000000): Input/output error .
../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 2 (00000040 00000000): Input/output error .
../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 150 (00000040 00000000): Input/output error .
../../../libdrm/intel/intel_bufmgr_gem.c:893: Error setting memory domains 1 (00000040 00000000): Input/output error .

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
 /dev/snd/controlC0: yelo3 1803 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
 Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 21'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:111d76b2,10280233,00100302 HDA:80862802,80860101,00100000'
   Controls : 24
   Simple ctrls : 15
Date: Wed Nov 25 18:36:55 2009
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Dell Inc. Latitude E6400
Package: linux-image-2.6.32-5-generic 2.6.32-5.6
 Socket 0:
   no product info available
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-generic root=UUID=c9ee61b8-026e-4d94-8d77-29d703d643a5 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-5.6-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.25
Reproducible: Yes
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: needs-upstream-testing regression-potential
TestedUpstream: No
Uname: Linux 2.6.32-5-generic x86_64 09/17/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17 0RX493
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/17/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr: Latitude E6400
dmi.sys.vendor: Dell Inc.

Nicolò Chieffo (yelo3) wrote :
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged

Thanks Leann.
I have to add that this problem is also valid when resuming from
suspend, but the result is worse: I cannot recover the PC in any way.

Andy Whitcroft (apw) on 2009-11-30
tags: added: kernel-lucid
Nicolò Chieffo (yelo3) wrote :

I've just done a further test, booting with 2.6.31-14-generic kernel
in lucid which seems to work, but has another problem. At least the
screen does not remain black after opening the lid.
Now I will stay with this kernel

tags: added: lucid
removed: kernel-lucid
Nicolò Chieffo (yelo3) wrote :

I also tested the current kernel 2.6.32-7-generic (which is based on
the final 2.6.32 if I'm not wrong).
The issue persists.

Note that this bug does not affect gnome-power-manager normal screen
blanking after a period of inactivity. It is only valid when closing
the laptop lid.

Changed in linux:
status: Unknown → Confirmed
Nicolò Chieffo (yelo3) wrote :

I've just tested the vanilla kernel, so I opened an upstram bug

Andy Whitcroft (apw) wrote :

@Nicolo -- is your machine set to suspend when the lid is closed? I am hearing similar reports of no screen on resume from suspend. Have you tested suspend?

Nicolò Chieffo (yelo3) wrote :

My machine does not suspend with lid close.
If I set up my machine to suspend with lid close the brightness error
is unrecoverable and I have to power cycle it.

Nicolò Chieffo (yelo3) wrote :

Is there anything else I can do for you?
I'm afraid that since this error is present in the final 2.6.32
kernel, I will have to cope with it in ubuntu 10.04 :(

Nicolò Chieffo (yelo3) wrote :

Working with upstream I figured out that passing "nomodeset" to boot
will avoid this bug

Nicolò Chieffo (yelo3) wrote :

mainline kernel does not have this problem

Nicolò Chieffo (yelo3) wrote :

Upstream asks if someone can "bisect the commits between 2.6.31 and
2.6.32 to check which one of them introduces the problem"

Nicolò Chieffo (yelo3) wrote :

They are not duplicate

Kai Jauch (kaijauch) wrote :

This should be interesting:

"I took a bit more at this problem, too, for the same machine Matthias is
checking (945GM). The problem looks like that the encoder->crtc is cleared at
lid close, but it's never recovered properly.

Namely, drm_crtc_helper_set_config() is called by intel's set_config, and this
calls drm_helper_disable_unused_functions() that prunes off crtcs used for
LVDs. Then, at lid open, drm_helper_resume_force_mode() is called, but this
resumes the CRTCs that are already enabled, thus it doesn't help for resuming

There is also a patch attached which, according to Takashi Iwai, fixes the problem. I don't know whether this is also the case for the GM45.

Chase Douglas (chasedouglas) wrote :

I'm CC'd on the upstream kernel bug Kai mentioned. If anything comes of it, I'll build a test kernel to see if it fixes the issue here.

Nicolò Chieffo (yelo3) wrote :

Could someone provide a kernel with the upstream patch applied, to test?

Changed in linux:
status: Confirmed → Invalid
Nicolò Chieffo (yelo3) on 2010-02-19
Changed in linux:
status: Invalid → Unknown
Changed in linux (Ubuntu):
assignee: nobody → Chase Douglas (chasedouglas)
Changed in linux:
status: Unknown → Fix Released
Chase Douglas (chasedouglas) wrote :

I have uploaded a test kernel to Please test it. The change has been sent upstream to the -stable queue, and if accepted it will automatically get pulled into Lucid. This would likely take a few weeks, but hopefully should happen before Lucid is released.

Changed in linux (Ubuntu):
status: Triaged → In Progress
Nicolò Chieffo (yelo3) wrote :

I'm installing it now, thanks

Nicolò Chieffo (yelo3) wrote :

This kernel seems to fix both this bug and

Unfortunately when I open the lid I still see the display notification:
"could not switch the monitor configuration / could not set the
configuration for CRTC 64"
and it feels that the PC is unresponsive for 4-5 seconds (slow keyboard input)

this is the output of dmesg:
[ 242.730766] [drm] TV-25: set mode NTSC 480i 0
[ 242.871973] [drm] TV-25: set mode NTSC 480i 0
[ 243.297676] dell-wmi: Unknown key ffd0 pressed
[ 244.420988] [drm] LVDS-8: set mode 1440x900 28
[ 245.053534] Skipping EDID probe due to cached edid
[ 245.138364] [drm] TV-25: set mode NTSC 480i 0
[ 245.279542] [drm] TV-25: set mode NTSC 480i 0
[ 245.384887] dell-wmi: Unknown key ffd1 pressed
[ 247.043936] Skipping EDID probe due to cached edid
[ 247.129234] [drm] TV-25: set mode NTSC 480i 0
[ 247.271197] [drm] TV-25: set mode NTSC 480i 0
[ 247.563727] Skipping EDID probe due to cached edid
[ 247.648526] [drm] TV-25: set mode NTSC 480i 0
[ 247.789917] [drm] TV-25: set mode NTSC 480i 0

Chase Douglas (chasedouglas) wrote :

Since this is fixed upstream and we are just waiting for the fix to drop into lucid, I'm moving this to triaged.

Changed in linux (Ubuntu):
assignee: Chase Douglas (chasedouglas) → nobody
status: In Progress → Triaged
tags: added: awaiting-upstream
tags: removed: needs-upstream-testing
Nicolò Chieffo (yelo3) wrote :

Can you please tell me which upstream patch you have applied? So I can
interact with upstream and tell my problems

Chase Douglas (chasedouglas) wrote :

@Nicolò Chieffo:

I applied this patch: It has not hit the intel-gfx git repo, so it still has a ways to go before it's incorporated to a point where it will be in the lucid kernel. If we get closer to the lucid release and it still isn't upstream we can take another look at including it in lucid ourselves.

Nicolò Chieffo (yelo3) wrote :

Hi back, recently my kernel got upgraded so I lost the patch and when
I open the lid I have to do the VT switch trick.

But now I noticed that it does not always work, because sometimes when
I switch to the VT, Xorg crashes and I obtain a .crash report.
Should I attach it here, file a new bug, or wait for the patch to land
to the new kernel and see if this still happens?

Chase Douglas (chasedouglas) wrote :

@Nicolò Chieffo:

FYI, the patch is taking a longer to get upstream than would be desired as there's some question as to whether it is the best fix for this issue.

I would assume at this point that X crashing is another symptom of this bug. If X still crashes when a patch fix is in the kernel, then it would be a new issue and would require a new bug.

Nicolò Chieffo (yelo3) wrote :

Ok, I will wait for a fix, then test again the Xorg problem.
In the mean time is there any possibility to disable screen blaking on
lid close?


Chase Douglas (chasedouglas) wrote :

I'm unaware of any way to force such behavior.

Chase Douglas (chasedouglas) wrote :

Although the fix hasn't reached upstream, I believe upstream is working on solving the solution through further development work to make things behave more "correctly". In the meantime, we need a fix for Lucid, so the patch was committed to the lucid kernel tree. Please test the next lucid kernel release (should be sometime in the next few days) to ensure it resolves this issue.

Changed in linux (Ubuntu):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :
Download full text (7.8 KiB)

This bug was fixed in the package linux - 2.6.32-15.21

linux (2.6.32-15.21) lucid; urgency=low

  [ Andy Whitcroft ]

  * Revert "(pre-stable) drm/i915: Increase fb alignment to 64k"
  * Revert "[Config] lenovo-sl-laptop -- enable"
  * Revert "ubuntu: lenovo-sl-laptop -- git tip (b19a08f81f)"
  * armel -- cramfs module will no longer be built
  * d-i -- make all modules optional
  * rename the debug packages to match archive standard
    - LP: #527837
  * lenovo-sl-laptop is no longer built

  [ Colin Ian King ]

  * Disable 4MB page tables for Atom, work around errata AAE44
    - LP: #523112

  [ Colin Watson ]

  * ubuntu: dm-raid4-5: Depend on XOR_BLOCKS
  * ubuntu: fsam7400: Depend on CHECK_SIGNATURE

  [ Jesse Barnes ]

  * SAUCE: drm/i915: don't change DRM configuration when releasing load
    detect pipe
    - LP: #488328

  [ Loïc Minier ]

  * [Config] armel Update versatile initrd configs
    - LP: #524893
  * SAUCE: [um] Don't use nx_enabled under UML
    - LP: #524849

  [ Manoj Iyer ]

  * [Config] added new config option CONFIG_SR_REPORT_TIME_LIMIT

  [ Mario Limonciello ]

  * SAUCE: v3 - Add Dell Business Class Netbook LED driver

  [ Rafael J. Wysocki ]

  * SAUCE: PM report driver and device suspend/resume times.

  [ Surbhi Palande ]

  * Revert "[Upstream] e1000e: enhance frame fragment detection"
    - CVE-2009-4538
  * Revert "[Upstream] e1000: enhance frame fragment detection"
    - CVE-2009-4536

  [ Tim Gardner ]

  * [Config] Enabled CONFIG_LEDS_DELL_NETBOOKS=m
  * SAUCE: (pre-stable) netfilter: xt_recent: fix buffer overflow
  * SAUCE: (pre-stable) netfilter: xt_recent: fix false match

  [ Upstream Kernel Changes ]

  * Revert "(pre-stable) eCryptfs: Add getattr function"
  * Fix potential crash with sys_move_pages
  * futex_lock_pi() key refcnt fix
  * futex: Handle user space corruption gracefully
  * futex: Handle futex value corruption gracefully
  * Fix race in tty_fasync() properly
  * hwmon: (w83781d) Request I/O ports individually for probing
  * hwmon: (lm78) Request I/O ports individually for probing
  * hwmon: (adt7462) Wrong ADT7462_VOLT_COUNT
  * ALSA: ctxfi - fix PTP address initialization
  * drm/i915: disable hotplug detect before Ironlake CRT detect
  * drm/i915: enable self-refresh on 965
  * drm/i915: Disable SR when more than one pipe is enabled
  * drm/i915: Fix DDC on some systems by clearing BIOS GMBUS setup.
  * drm/i915: Add HP nx9020/SamsungSX20S to ACPI LID quirk list
  * drm/i915: Fix the incorrect DMI string for Samsung SX20S laptop
  * drm/i915: Add MALATA PC-81005 to ACPI LID quirk list
  * usb: r8a66597-hcd: Flush the D-cache for the pipe-in transfer buffers.
  * i2c-tiny-usb: Fix on big-endian systems
  * drm/i915: handle FBC and self-refresh better
  * drm/i915: Increase fb alignment to 64k
  * drm/i915: Update write_domains on active list after flush.
  * regulator: Fix display of null constraints for regulators
  * ALSA: hda-intel: Avoid divide by zero crash
  * CPUFREQ: Fix use after free of struct powernow_k8_data
  * freeze_bdev: don't deactivate successfully frozen MS_RDONLY sb
  * cciss: Make cciss_seq_show handle holes in the h->drv[] array
  * ioat: fix in...


Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Nicolò Chieffo (yelo3) wrote :

For interested people, the other part of the bug (the gnome-settings-daemon notification and input slowdown) is in bug #524830

Kai Jauch (kaijauch) wrote :

Nicolò, is this fixed for you?
I am still encountering this problem with kernel 2.6.32-16.25. The kernel from Chase Douglas fixes the issue, the current kernel in lucid does not.

Kai Jauch (kaijauch) wrote :

Also working in -15, but broken again in -16. The display stays off, only a vt switch turns it back on.

Nicolò Chieffo (yelo3) wrote :

In my case X crashes when opening the lid, so I don't know

Chase Douglas (chasedouglas) wrote :

@Kai Jauch:

The 2.6.32-16 kernel has the 2.6.33 drm (graphics drivers) stack in it. This was done for many varied reasons, one of which is better support for intel graphics. If you are having issues now, I suggest opening a new bug just to keep things separate and not get too tangled up with the fix for the old graphics drivers.

@Nicolò Chieffo:

You can test this by switching to another VT, closing the lid, and opening it back up. I think this should exercise the same bits as doing it in X. If X still crashes and screws things up you can stop it temporarily: "sudo stop gdm"

Nicolò Chieffo (yelo3) wrote :

I confirm that if you switch quickly to VT Xorg does not crash.

Nicolò Chieffo (yelo3) wrote :

If you are interested, I filed another bug fox xorg crash:

Kai Jauch (kaijauch) wrote :

@Chase Douglas:

Filed as bug #540134.

Andy Whitcroft (apw) wrote :

This change got lost in the major DRM update to v2.6.33. Reapplied for lucid.

Changed in linux (Ubuntu):
status: Fix Released → Fix Committed
Launchpad Janitor (janitor) wrote :
Download full text (3.3 KiB)

This bug was fixed in the package linux - 2.6.32-19.28

linux (2.6.32-19.28) lucid; urgency=low

  [ Andy Whitcroft ]

  * [Config] enable various multitouch devices
    - LP: #541453

  [ Chase Douglas ]

  * (pre-stable): input: ALPS - Add signature for HP Pavilion dm3 laptops
    - LP: #545307
  * SAUCE: Disable function tracing after hitting __schedule_bug
  * SAUCE: Reduce ACPI resource conflict message to KERN_INFO, printf
    - LP: #440470

  [ Jesse Barnes ]

  * SAUCE: drm/i915: don't change DRM configuration when releasing load
    detect pipe
    - LP: #488328

  [ John Johansen ]

  * SAUCE: AppArmor: Remove null_profile's use of PFLAG_NO_LIST_REF
    - LP: #539437
  * SAUCE: AppArmor: Stop page allocation warnings that can occur on policy
    - LP: #458299
  * SAUCE: AppArmor: Return string len rather than the allocation size
    - LP: #551844
  * SAUCE: AppArmor: Fix oops in profile verification if profile unpack

  [ Luke Yelavich ]

  * [Config] Enable Nouveau DRM module on powerpc

  [ Stefan Bader ]

  * SAUCE: Pull in thinkpad-acpi from v2.6.34-rc1
    - LP: #357673
  * [Config] Enable thinkpad-acpi ALSA volume control
    - LP: #357673

  [ Steve Conklin ]

  * SAUCE: drm/i915: Disable FBC on 915GM and 945GM
    - LP: #492392, #539609

  [ Upstream Kernel Changes ]

  * Revert "(pre-stable) drm/i915: blacklist lid status: Sony VGN-BX196VP,
    Dell Inspiron 700m"
    - LP: #515246
  * (pre-stable) softlockup: Stop spurious softlockup messages due to
    - LP: #551068
  * backlight: mbp_nvidia_bl - add five more MacBook variants
    - LP: #511965
  * drm/nv04-nv40: Fix up the programmed horizontal sync pulse delay.
    - LP: #529130
  * drm/nouveau: Fix fbcon corruption with font width not divisible by 8
    - LP: #544739
  * (pre-stable) USB: fix usbfs regression
  * drm/radeon/bo: add some fallback placements for VRAM only objects.
    - LP: #507148
  * drm/radeon/kms: don't print error on -ERESTARTSYS.
    - LP: #507148
  * Input: add the ABS_MT_PRESSURE event
    - LP: #541453
  * HID: Support for 3M multitouch panel
    - LP: #541453
  * HID: make 3M PCT touchscreen driver standalone config option
    - LP: #541453
  * HID: add support for Stantum multitouch panel
    - LP: #541453
  * HID: make Stantum driver standalone config option
    - LP: #541453
  * HID: add support for Acer T230H multitouch
    - LP: #541453
  * HID: add support for Pixart Imaging Optical Touch Screen
    - LP: #541453
  * HID: fixed bug in single-touch emulation on the stantum panel
    - LP: #541453
  * HID: add pressure support for the Stantum multitouch panel
    - LP: #541453
  * HID: Support for MosArt multitouch panel
    - LP: #541453
  * HID: hid-ntrig add multi input quirk and clean up
    - LP: #541453
  * HID: n-trig: remove unnecessary tool switching
    - LP: #541453
  * HID: hid-ntrig: multitouch cleanup and fix
    - LP: #541453
  * HID: hid-ntrig: Single touch mode tap
    - LP: #541453
  * hid: ntrig touch events
    - LP: #541453
  * (pre-stable) x86-32, resume: do a global tlb flush in S4 resume
    - LP: #531309
  * drm/i915: Part of: Add initial bits for VGA mode...


Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Changed in linux:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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