Lid state incorrectly reported as closed on HP-Compaq 6120

Bug #206511 reported by Gerhard Kremer
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned
Hardy
Invalid
Undecided
Unassigned
Intrepid
Invalid
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Medium
Unassigned
Hardy
Won't Fix
Undecided
Unassigned
Intrepid
Fix Released
Medium
Unassigned
linux-source-2.6.15 (Ubuntu)
Invalid
Undecided
Unassigned
Hardy
Invalid
Undecided
Unassigned
Intrepid
Invalid
Undecided
Unassigned

Bug Description

When I close the lid, its state as reported by /proc/acpi/button/lid/C1E5/state changes to "closed"; however, when I open it again, it stays at "closed", which keeps ACPI executing lid events which blank the screen every few minutes (I suspect that whenever a thermal event is received) and make it impossible to work. I have to reboot to reset the lid state back to open.

I am using an up-to-date Kubuntu Hardy beta, but have observed this behavior since Gutsy (linux-source-2.6.22) on both Ubuntu and Kubuntu. The computer is an HP-Compaq nc6120, with an Intel Centrino 2GHz CPU.

Attached find the output of dmesg in my system.

possible WORKAROUND (from http://tinyurl.com/38frty - Please note, that this may cause your video to break, so make sure that you don't have unsaved things opened. Read the description for it first.):
echo 1 | sudo tee /proc/acpi/video/*/DOS

Revision history for this message
Gerhard Kremer (gerhardusm2002) wrote :
Revision history for this message
Gerhard Kremer (gerhardusm2002) wrote :

Forgot to add a sample of /var/log/acpid during the blackouts:

Revision history for this message
Gerhard Kremer (gerhardusm2002) wrote :

Found a workaround. The cause of the problem is detailed in

http://tinyurl.com/38frty ,

where they also suggest a way to fix it until they revise the kernel.

See also the discussion in
http://ubuntuforums.org/showthread.php?t=587390&page=3

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Gerhard,

We're almost at the kernel freeze for Hardy and only critical bug fixes or extremely simple patches are being pulled in at this point. It's likely you'll need to continue using the workaround for Hardy. Once the Intrepid Ibex development kernel comes out, shortly after the Hardy final release, we'll try to get this resolved and working out of the box. Thanks.

Changed in linux:
milestone: none → later
status: New → Confirmed
Revision history for this message
Gerhard Kremer (gerhardusm2002) wrote :

Leann,

Fair enough. Thank you, and good luck for the release!

Revision history for this message
Martin Soto (soto255) wrote :

Just for the record: the same workaround was necessary on my HP/Compaq nc6220 (similar but not identical model) in order to make the lid work properly under Hardy. The problem was a bit different, since the kernel reported the lid state as always open, regardless of the actual state of the lid button. Similar to the original report, though, closing the lid once caused spurious lid events to be sent about every 30 seconds, which, in turn, caused very annoying screen flickering.

Many thanks to Gerhard for mentioning the workaround. This issue was making me crazy.

Changed in linux-source-2.6.15:
status: New → Invalid
Revision history for this message
Martin Soto (soto255) wrote :

I wanted to report this for 2.6.24, but ended up doing the wrong action and now cannot revert it. Lauchpad is quite unforgiving sometimes. Sorry for the noise, anyway.

Daniel Hahler (blueyed)
Changed in linux:
importance: Undecided → Medium
status: Confirmed → Triaged
description: updated
description: updated
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Removing linux-source-2.6.24 task since beginning with Hardy, kernel bugs should be reported against the "linux" package which this already is.

Also, I just wanted to let you know the kernel team is currently pulling together the Intrepid kernel. We'll hopefully having something for you to test shortly. Thanks for your patience.

Thanks.

Changed in linux-source-2.6.24:
status: New → Invalid
Changed in linux:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Gerhard,

Care to test the Intrepid Ibex 8.10 kernel, it is currently available in the following PPA:

https://edge.launchpad.net/~kernel-ppa/+archive

If you are not familiar with how to install packages from a PPA basically do the following:

Create the file /etc/apt/sources.list.d/kernel-ppa.list to include the following two lines:

deb http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main
deb-src http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main

Then run the command:

sudo apt-get update

You should then be able to install the linux-image-2.6.25 kernel package. Please let us know your results. Thanks.

Revision history for this message
Gerhard Kremer (gerhardusm2002) wrote :

Leann,

Thank you for the quick answer.

Due to other issues, I had to drop Hardy and go back to Gutsy; it still has the same issue though, so I'll be happy to test your kernel ASAP.

However, when I try to install the binary package, it complains that module-init-tools has too low a version number (needs >=3.3-pre11-4ubuntu3). Is it the same if I download your kernel source and compile it in my machine? If not, will upgrading my module-init-tools as well as the kernel break something in my system?

Revision history for this message
Gerhard Kremer (gerhardusm2002) wrote :

Leann,

I downloaded the PPA kernel source, compiled it, and tested it under Gutsy. It works! The bug is no more; the lid button works exactly as it should without needing the above workaround in rc.local.

Here is the output to /var/log/acpid under the new kernel when I press the lid button and release it a second later:

-----------------------------------------------------------------
[Mon May 12 15:14:34 2008] received event "button/lid C1E5 00000080 00000012"
[Mon May 12 15:14:34 2008] notifying client 4753[107:116]
[Mon May 12 15:14:34 2008] notifying client 4786[0:0]
[Mon May 12 15:14:34 2008] executing action "/etc/acpi/lid.sh"
[Mon May 12 15:14:34 2008] BEGIN HANDLER MESSAGES
ERROR: Couldn't attach to DCOP server!
[Mon May 12 15:14:34 2008] END HANDLER MESSAGES
[Mon May 12 15:14:34 2008] action exited with status 1
[Mon May 12 15:14:34 2008] completed event "button/lid C1E5 00000080 00000012"
[Mon May 12 15:14:34 2008] received event "button/lid C1E5 00000080 00000013"
[Mon May 12 15:14:34 2008] notifying client 4753[107:116]
[Mon May 12 15:14:34 2008] notifying client 4786[0:0]
[Mon May 12 15:14:34 2008] executing action "/etc/acpi/lid.sh"
[Mon May 12 15:14:34 2008] BEGIN HANDLER MESSAGES
ERROR: Couldn't attach to DCOP server!
[Mon May 12 15:14:35 2008] END HANDLER MESSAGES
[Mon May 12 15:14:35 2008] action exited with status 1
[Mon May 12 15:14:35 2008] completed event "button/lid C1E5 00000080 00000013"
---------------------------------------------------------------------

Thank you very much for your help! I can hardly wait for Intrepid to come out now . . . ;-)

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Gerhard,

Thanks for testing and the feedback. I'm glad to hear this is at least resolved in the upcoming Intrepid kernel for you. I've gone ahead and updated this report to reflect this being "Fix Released" for Intrepid. I imagine the Intrepid kernel should hit the archives shortly so you won't have to install from the PPA. If you notice any sort of regressions regarding this bug as development continues for the Intrepid kernel please feel free to reopen this bug (ie switch status from "Fix Released" to "New"). Thanks.

Changed in linux-source-2.6.15:
status: New → Invalid
Changed in linux:
status: New → Won't Fix
status: Triaged → Fix Released
Revision history for this message
Kieran Fleming (kieran-fleming) wrote :

It works fine for me too, thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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