ACPI lid event occurs constantly until system crashes

Bug #388724 reported by kmcphillips
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu
Incomplete
Undecided
Unassigned

Bug Description

Running Jaunty Netbook Remix cleanly installed on an Acer Aspire One D150.

When running acpi_listen on a fresh boot, no events are logged. When the lid is closed and opened, events like this continue at dozens a second for several minutes:

button/lid LID0 00000080 0000036e
button/lid LID0 00000080 0000036f
button/lid LID0 00000080 00000370
button/lid LID0 00000080 00000371
button/lid LID0 00000080 00000372
button/lid LID0 00000080 00000373
button/lid LID0 00000080 00000374
button/lid LID0 00000080 00000375
button/lid LID0 00000080 00000376

The events continue as long as the lid is closed and the computer is awake. This causes kacpid and kacpi_notify to consume memory and CPU until the system crashes. Usually caused by many oom-killer calls.

The laptop does not sleep automatically despite the power management setting set to suspend on lid close. When the lid.sh script is modified to call sleep directly, the system gets in a near infinte loop of waking up and responding to the lid event and sleeping. Suspend and hibernate work correctly if triggered manually.

I can attach whatever other information is needed.

Revision history for this message
Kenneth (kenneth-hexad) wrote :
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

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.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
firespeaker (firespeaker) wrote :
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thanks for the reply

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.