Intrepid: resume after suspend inconsistent behaviour on Thinkpad

Bug #291133 reported by Andreas Jonsson
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I can suspend my Lenovo Thinkpad T61, either using Suspend from the the Power Manager Applet or the Fn+F4 key. However, only in the former case does the laptop resume properly. When I use Fn+F4 the resume initiates, the drive starts running and the screen comes on for about half a second, and then it falls back into suspended mode. Now, if a try to resume it a again, it works. How can I make resume work flawlessly with the Fn+F4 button?

$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

$ lshal | grep system.hardware
  system.hardware.primary_video.product = 10754 (0x2a02) (int)
  system.hardware.primary_video.vendor = 32902 (0x8086) (int)
  system.hardware.product = '7658CTO' (string)
  system.hardware.serial = 'L3AAE8Y' (string)
  system.hardware.uuid = '3D818E01-49B5-11CB-801D-8D747437C9AF' (string)
  system.hardware.vendor = 'LENOVO' (string)
  system.hardware.version = 'ThinkPad T61' (string)

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

I have assigned this to the linux kernel team as it seems to be improper response to the hardware keypress.

Revision history for this message
Andreas Jonsson (sonofjon) wrote :

Pleas find attached the outputs requested: uname -a > uname-a.log

Revision history for this message
Andreas Jonsson (sonofjon) wrote :

cat /proc/version_signature > proc_version_signature.log

Revision history for this message
Andreas Jonsson (sonofjon) wrote :

sudo lspci -vvnn > lspci-vvnn.log

Revision history for this message
Andreas Jonsson (sonofjon) wrote :

dmesg > dmesg.log

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for your supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in linux:
assignee: nobody → ubuntu-kernel-acpi
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
François Garillot (garillot) wrote :

I'm facing the same problem on a Lenovo X61 tablet.

$ lshal | grep system.hardware
  system.hardware.primary_video.product = 10754 (0x2a02) (int)
  system.hardware.primary_video.vendor = 32902 (0x8086) (int)
  system.hardware.product = '776295G' (string)
  system.hardware.serial = 'L3A1444' (string)
  system.hardware.uuid = '26B43C01-48CE-11CB-8B9C-F0E2AAF4D219' (string)
  system.hardware.vendor = 'LENOVO' (string)
  system.hardware.version = 'ThinkPad X61 Tablet' (string)
$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
$ uname -a
Linux ash 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux
$ cat /proc/version_signature
Ubuntu 2.6.27-7.16-generic

Revision history for this message
François Garillot (garillot) wrote :

x61_lspci-vvnn.log

Revision history for this message
Jukka Laurila (jlaurila) wrote :

Same problem on a T40p. Suspend by closing/opening the lid works just fine but Fn-F4 exhibits this weird "bounce" behavior.

Revision history for this message
Andy Walker (walkeraj) wrote :

I am experiencing the same issues on a Thinkpad x31. Please let me know if I can provide any more information.

Revision history for this message
Andy Walker (walkeraj) wrote :
Revision history for this message
Andy Walker (walkeraj) wrote :
Revision history for this message
Andy Walker (walkeraj) wrote :
Revision history for this message
cookieofdoom (thecookieofdoom) wrote :

This thread might be useful to anyone looking into the issue... http://bbs.archlinux.org/viewtopic.php?id=58129 It seems they've solved it. Has anyone else tried this? I'm not sure if this is what's wrong in Ubuntu, and I'm not sure how to fix it if it is.

I've had the same issue and can upload information files if someone thinks they'll be helpful. I don't have Ubuntu running on my laptop right now, but will help out if needed.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
Curtis Hovey (sinzui)
Changed in linux (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.