Feisty breaks hibernate on Thinkpad X30

Bug #103672 reported by Dave Love
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: acpi-support

Hibernate worked on this system in Edgy but fails in Feisty. It just brings up the
screen lock, after which there's a `HAL failed to hibernate.' popup displayed.

If you can tell me what info is useful, I'll send it when I'm online after Easter.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Dave, this report needs information very much like what I've just requested for bug# 103672, with one addition (noted in [1]):

First, please confirm that you have up-to-date BIOS, and update the report with the output of "uname -a".

Next, please attach the output of the following commands:

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Please be sure to use sudo, root privileges are required to obtain the necessary information. Please attach one file per command, please do not compress the output, please do not add the output in-line, and please do not attempt to email in the attachments - they have to be added to the report within Launchpad.

Please attempt a hibernate/resume cycle, reboot, then attach the file

    /var/log/kern.log.0

This will contain information about the failed hibernate/resume cycle.

Sorry for requesting what might seem like duplicate effort, but for the moment we'll assume two separate bugs, which means we need complete information in both reports.

Thanks!

[1] https://wiki.ubuntu.com/DebuggingACPI

Changed in acpi-support:
assignee: nobody → pwwnow
status: Unconfirmed → Needs Info
Revision history for this message
Dave Love (fx-gnu) wrote :

The behaviour has changed between when i reported it and the current 2.6.20-15-generic.
Now it appears to hibernate after a great deal of disk activity, but it doesn't resume,
just reboots.

I'll attach the requested info. This system is quite a disincentive to report bugs,
contrasted with Debian...

Revision history for this message
Dave Love (fx-gnu) wrote :
Revision history for this message
Dave Love (fx-gnu) wrote :
Revision history for this message
Dave Love (fx-gnu) wrote :

kern.log.0 is the wrong one. Here's the relevant part of kern.log.

I should have said my BIOS is one point off the latest, but the difference is just support
for a device I don't have.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Confirmed based on available logs. QA/devs, this is a regression from Edgy, please set importance medium/high.

Changed in acpi-support:
assignee: pwwnow → ubuntu-kernel-team
status: Needs Info → Confirmed
Revision history for this message
Petr Ferschmann (petr-ferschmann) wrote :

I have Thinkpad X31 and I have problem too.

I will attach requested files too.

Revision history for this message
Petr Ferschmann (petr-ferschmann) wrote :
Revision history for this message
Petr Ferschmann (petr-ferschmann) wrote :
Revision history for this message
Petr Ferschmann (petr-ferschmann) wrote :

uname -a
Linux elara.in.softeu.cz 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Revision history for this message
Petr Ferschmann (petr-ferschmann) wrote :

In my case the laptop goes to sleep and doesn't wakeup. Sometime (1 of 10) it wakeups successfully. In edgy, dapper and breezy it worked without any problem.

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
Peter Whittaker (pwwnow) wrote :

Closing (marking as invalid) due to lack of activity - last user update was 19 months ago (April 2007).

Changed in linux:
status: Incomplete → Invalid
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.

Revision history for this message
Ivan Kharlamov (the-paper-men) wrote :

I've got the same problem on 9.04.

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.