Laptop does not goto suspend or hibernate when lid is closed

Bug #43316 reported by Hameed محمد حمید
8
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Medium
Unassigned

Bug Description

I have a DELL inspiron 8600; when the laptop lid is closed the system neiter suspends nor hibernates.

Revision history for this message
Daniel Robitaille (robitaille) wrote :

Thank you for your bug report. Which version of Ubuntu are you using?

Revision history for this message
Hameed محمد حمید (hameeduddin) wrote : Re: [Bug 43316] Re: Laptop does not goto suspend or hibernate when lid is closed

I'm using Dapper Beta2. Thanks for the quick response.

Daniel Robitaille <email address hidden> wrote: Thank you for your bug report. Which version of Ubuntu are you using?

--
Laptop does not goto suspend or hibernate when lid is closed
https://launchpad.net/bugs/43316

---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1&cent;/min.

Revision history for this message
Daniel Robitaille (robitaille) wrote :

If you click on "systems" in the top panel, then preference and finally power management, you will get to the "power management preferences" window. In there you can select what you laptop should do when the lid is closed (both when running on AC, or when running on battery). By default these 2 options are set to "blank screen" when closing the lid. Have you tried to change these options to the option you want (either hibernate or suspend)?

Revision history for this message
Mikko Saarinen (mikk0) wrote :
Download full text (4.4 KiB)

I have this same problem with MSI S250. Also using Dapper Beta.

The laptop hibernates the first time lid is closed after the machine has been restarted, but after that there is no action whatsoever. Even dmesg doesn't show anything.

This is the dmesg notifying about the first lid close and resume events. After this no matter how many times I close the lid there are no more messages:

[4294771.910000] pcmcia: Detected deprecated PCMCIA ioctl usage.
[4294771.910000] pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
[4294771.910000] pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
[4294771.910000] pccard: card ejected from slot 0
[4294773.180000] ACPI: PCI interrupt for device 0000:00:0e.0 disabled
[4294776.577000] Freezing cpus ...
[4294776.578000] Stopping tasks: ========================================================================================|
[4294776.579000] Shrinking memory... done (28768 pages freed)
[4294776.757000] ACPI: PCI interrupt for device 0000:00:09.1 disabled
[4294776.757000] ACPI: PCI interrupt for device 0000:00:09.0 disabled
[4294776.757000] ACPI: PCI interrupt for device 0000:00:03.3 disabled
[4294776.768000] ACPI: PCI interrupt for device 0000:00:03.1 disabled
[4294776.768000] ACPI: PCI interrupt for device 0000:00:03.0 disabled
[4294776.768000] ACPI: PCI interrupt for device 0000:00:02.7 disabled
[4294776.768000] swsusp: Need to copy 51409 pages
[4294776.768000] swsusp: Restoring Highmem
[4294840.768000] **** SET: Misaligned resource pointer: d75bc702 Type 07 Len 0
[4294840.768000] **** SET: Misaligned resource pointer: d75bc702 Type 07 Len 0
[4294840.768000] **** SET: Misaligned resource pointer: d75bc702 Type 07 Len 0
[4294840.768000] **** SET: Misaligned resource pointer: d75bc702 Type 07 Len 0
[4294840.768000] **** SET: Misaligned resource pointer: d75bc702 Type 07 Len 0
[4294840.768000] **** SET: Misaligned resource pointer: d75bc702 Type 07 Len 0
[4294840.768000] **** SET: Misaligned resource pointer: d75bc702 Type 07 Len 0
[4294840.786000] ACPI: PCI Interrupt 0000:00:02.7[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
[4294841.038000] ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKE] -> GSI 5 (level, low) -> IRQ 5
[4294841.039000] ACPI: PCI Interrupt 0000:00:03.1[B] -> Link [LNKF] -> GSI 7 (level, low) -> IRQ 7
[4294841.050000] ACPI: PCI Interrupt 0000:00:03.3[D] -> Link [LNKH] -> GSI 5 (level, low) -> IRQ 5
[4294841.050000] ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
[4294841.050000] ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
[4294841.050000] ACPI: PCI Interrupt 0000:00:09.1[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
[4294841.050000] ACPI: PCI Interrupt 0000:00:09.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
[4294841.688000] ACPI-0517: *** Error: Method parse/execution failed [\_SB_.PCI0.IDEC.IDE0._STM] (Node ddfb8aa0), AE_AML_PACKAGE_LIMIT
[4294841.970000] ACPI-0517: *** Error: Method parse/execution failed [\_SB_.PCI0.IDEC.IDE1._STM] (Node ddfb8960), AE_AM...

Read more...

Revision history for this message
Mikko Saarinen (mikk0) wrote :

This is a new bug since my machine was working great a week ago. This has happened after the bug 35213 (https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/35213) got fixed.

I also think that this is related to the fact that my usb mouse stops working after hibernation.

Mikko

Revision history for this message
Daniel Robitaille (robitaille) wrote :

> This is a new bug since my machine was working great a
> week ago.

Mikko, please file a new bug for your problem since it is far from being clear that this is the same problem than this one. (for one thing, it is a totally different hardware).

Revision history for this message
Mikko Saarinen (mikk0) wrote :

Thank you for the suggestion, I filed a bug 43391.

Mikko Saarinen

Revision history for this message
Hameed محمد حمید (hameeduddin) wrote :

I don't see a "power management preferences" under system -> preferences.
I had done a dist-upgrade from breezy.

Daniel Robitaille <email address hidden> wrote: If you click on "systems" in the top panel, then preference and finally
power management, you will get to the "power management preferences"
window. In there you can select what you laptop should do when the
lid is closed (both when running on AC, or when running on battery). By
default these 2 options are set to "blank screen" when closing the lid.
Have you tried to change these options to the option you want (either
hibernate or suspend)?

--
Laptop does not goto suspend or hibernate when lid is closed
https://launchpad.net/bugs/43316

---------------------------------
Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.

Revision history for this message
Daniel Robitaille (robitaille) wrote :

I would guess that when you did your dist-upgrade, you didn't have the meta-package ubuntu-desktop installed, right?
You can check this by running these 2 commands from a terminal:
 apt-cache policy gnome-power-manager
 apt-cache policy ubuntu-desktop

To get that power-management preference window I described earlier, you will need to install gnome-power-manager (and possibly reboot your computer afterward).

Revision history for this message
Hameed محمد حمید (hameeduddin) wrote :

Thanks. Yes, i didn't have ubuntu-desktop installed earlier. After installing 'gnome-power-manager' i was able to get the laptop into suspend/hibernate mode when the lid is closed. However on opening the lid the the laptop starts up but i get a blank screen. In short my laptop does not resume from suspend/hibernate. Do i have to open another bug for this.

Thanks.
Hameed

Daniel Robitaille <email address hidden> wrote: I would guess that when you did your dist-upgrade, you didn't have the meta-package ubuntu-desktop installed, right?
You can check this by running these 2 commands from a terminal:
 apt-cache policy gnome-power-manager
 apt-cache policy ubuntu-desktop

To get that power-management preference window I described earlier, you will need to install gnome-power-manager (and possibly reboot your computer afterward).

--
Laptop does not goto suspend or hibernate when lid is closed
https://launchpad.net/bugs/43316

---------------------------------
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

Revision history for this message
Daniel Robitaille (robitaille) wrote :

That looks like bug 42490. If that's the case, we can close this report, and you can subscribe to the other one.

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.