Feisty: cannot hibernate nor suspend (worked fine in Edgy)

Bug #114096 reported by przemjaskier
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: acpi

Kubuntu Feisty. Toshiba Tecra A7.

In Edgy it worked perfectly on the same hardware.

After clicking "hibernate" or "suspend". I got KDE's lock screen immediately. Then when I try to unlock and simply close system, it hangs until I press control-alt-backspace, the it shows something like:

~"Waiting for eth0 to became free, usage count = 1"

and keeps repeating this until I press control-alt-delete. When rebooting it tries to behave like when it comes from hibernation (white strip on the splash screen), but reboots immediately instead of booting KDM. Following reboots work fine, until next hibernate attempt.

Attachements follows.

Revision history for this message
przemjaskier (przemjaskier) wrote :

BIOS is up-to-date.

uname -a
Linux longclaw 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Revision history for this message
przemjaskier (przemjaskier) wrote :
Revision history for this message
przemjaskier (przemjaskier) wrote :
Revision history for this message
przemjaskier (przemjaskier) wrote :
Revision history for this message
przemjaskier (przemjaskier) wrote :

Note: problem was present from the very beggining, on a clean installation of Feisty.

Changed in acpi:
assignee: nobody → ubuntu-kernel-acpi
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
H.E. Pennypacker (klop2964) wrote :

Same problem here with a Dell Inspiron 2200, Intel 950GM graphics card. Everything was fine on Edgy.

Revision history for this message
przemjaskier (przemjaskier) wrote :

Strange, but it looks like the source of this problem is running fireflier demon. When I turn it off, hibernate works (but a lot of other scary errors appear during hibernate/restore process).

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 - http://www.ubuntu.com/testing . 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.

--or--

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 http://www.ubuntu.com/testing 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
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
Curtis Hovey (sinzui)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
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.