macbook 3.1: Resume from suspend sometimes fails.

Bug #205072 reported by Ian Ohr
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mactel Support
linux (Ubuntu)
Won't Fix
linux-source-2.6.22 (Ubuntu)
Won't Fix

Bug Description

On my macbook 3.1 suspend and resume works over 50% of the time, however when it does not work, this happens:

* I open the lid of my macbook 3,1
* The led next to the infra-red port goes out
* The dvd drive makes it's usual noise
* Then nothing

The screen does not display anything, it is as if the screen is not given power. The bug seems to be a more comprehensive failure of the resume as I cannot power the system down using known working keyboard shortcuts.

There is a similar bug
but this similar bug allows you to see something on the screen if you look carefully. It is just the backlight that does not come on.

I don't know how to debug this but I assume I would have to perform some sort of pre-emptive strike. Establishing something that observes the state of things when the system is suspended, then logging that state if resume succeeds. From this log one could perhaps see that one state is not listed.

I suspect it is something to do with one of the following:
* Connected to mains power during suspend
* Disconnected/Connected to mains power while suspended
* On battery power during resume
* On mains power during resume
* Any other combination of power state, including charge level of battery.

Revision history for this message
Ricky Campbell (cyberdork33) wrote :

You really need to try to mark this against an Ubuntu package as well. Are you on Hardy? What graphics card is it?

Revision history for this message
Ian Ohr (munk3h) wrote :

I'm using Gutsy.
The Graphics card is reported as the following, by lspci:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

As far as assigning this to a package, I can't see a field for package in the "Edit description/tags" page, and the only other link I can see relating to package is "Also affects: + Distribution/Package…" in the top right. I this second link the one I should use?

Also I don't know which package suspend-resume issues should be filed under

Ian Ohr (munk3h)
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at . Thanks in advance!

Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in linux-source-2.6.22:
status: Incomplete → Invalid
Changed in mactel-support:
status: New → Incomplete
Revision history for this message
Edy Tanto (otnatyde) wrote :

I'm having the problem as reported by Ian Ohr. To be more precise, here is what happen when I try to resume from suspend:

1. The mouse is extremely unresponsive
2. Keyboard works fine, however so I can still press the power button to bring up the shutdown menu then followed by Alt-R to Restart.

Here's the output of the 'uname -a' command:
Linux edy-linux 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

The other two logs files 'dmesg.log' and 'lspci-vvnn.log' are attached. Thanks in advance. The Ubuntu community is indeed amazing!

Revision history for this message
Edy Tanto (otnatyde) wrote :

and here's the 'lspci-vvnn.log'

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Invalid → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

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

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.


2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

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 for more information. Thanks.

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

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
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.