Bug 15553 - Screen backlight doesn't come back on after lid was closed (GM45)
Screen backlight doesn't come back on after lid was closed (GM45)
Status: CLOSED CODE_FIX
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel)
All Linux
: P1 normal
Assigned To: drivers_video-dri-intel@kernel-bugs.osdl.org
:
Depends on:
Blocks: 15310
  Show dependency treegraph
 
Reported: 2010-03-17 14:35 UTC by bugs
Modified: 2010-05-04 20:58 UTC (History)
6 users (show)

See Also:
Kernel Version: 2.6.34-rc2
Tree: Mainline
Regression: Yes


Attachments

Description bugs 2010-03-17 14:35:20 UTC
On a Dell Latitude E6400 with a GM45 closing the display lid turns the backlight off, opening the lid however doesn't turn it back on. I have to switch to another VT to turn it back on, then switch back to X.

This was tested with the latest mainline kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-03-15/linux-image-2.6.34-999-generic_2.6.34-999.201003151003_amd64.deb).


Originally reported at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/488328 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/540134.

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Comment 1 Nicolo' Chieffo 2010-03-17 15:40:14 UTC
If you don't quickly switch to the VT, xorg will crash.
I've collected logs before closing and opening the lid, see those links:
http://launchpadlibrarian.net/41121035/pre.tar.gz
http://launchpadlibrarian.net/41121036/closed.tar.gz
http://launchpadlibrarian.net/41121037/open.tar.gz
Comment 2 ykzhao 2010-03-22 07:43:51 UTC
Can you add the boot option of "drm.debug=0x04" and do the following test?
     1. get the output of "cat /proc/acpi/button/LID/*/state", dmesg, intel_reg_dumper before close the LID
     2. close the LID
     3. Open the LID
     4. Please login the system by using ssh and get the output of " cat /proc/acpi/button/LID/*/state", dmesg, intel_reg_dumper again.

Thanks
Comment 3 Nicolo' Chieffo 2010-03-22 09:06:43 UTC
The logs I linked are done with drm.debug=0x04
Comment 4 ykzhao 2010-04-02 07:23:49 UTC
The other info is also required. For example: LID state, intel_reg_dumper

At the same time it seems that the option of "drm.debug=0x06" is added in the links log. Will you please change it to "drm.debug=0x04"? Otherwise the useful info is flushed.

thanks.
Comment 5 Nicolo' Chieffo 2010-04-02 08:37:31 UTC
My distribution was able to fix this bug.
Some information might be here: https://bugs.launchpad.net/bugs/488328
Comment 6 Dan Carpenter 2010-05-03 19:50:34 UTC
I looked and it seems like this is a combination of these two bugs:

Crashing bug:
https://bugzilla.kernel.org/show_bug.cgi?id=14997

Windows Vista has changed the keycodes around and gnome-settings-daemon needs to be updated to match.  (Not a kernel bug).
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477

Both bugs have a fix now, so can we close this bug?

Note You need to log in before you can comment on or make changes to this bug.