[Gutsy] Suspend fails on Lenovo Thinkpad T60p w/ ATI Mobility

Bug #173722 reported by ezzieyguywuf
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

This is my first bug report and I am relatively new to Ubuntu, so I'm sorry because I know I have not included a bunch of files in here that will be needed (please tell me what to post). Basically, I was getting suspend to ram to work in Feisty using uswsusp, but now that I am in Gutsy I cannot suspend to ram no matter what I try (I had to do some tricky stuff to even get the s2ram function on uswsusp to appear). Any help would be appreciated b/c i tend to leave my laptop on all day and would like to suspend it as its temperatures have been excessively high as of late (perhaps another bug?)

Revision history for this message
Nanley Chery (nanoman) 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 didn't include enough information.

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

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

sorry for the delay, but I have added the requested attachments. Thank you for your help :-)

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

tar: /proc/acpi/event: Cannot open: Device or resource busy

I got that error when I made the tarball, hope that doesn't ruin anything.

Revision history for this message
Nanley Chery (nanoman) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux-source-2.6.22.

Revision history for this message
Tobias McNulty (tmcnulty1982) wrote :

I'm posting a comment here as requested by Leann's recent comment on bug #33372. I have a ThinkPad T60 that still fails to resume from suspend with the Gutsy kernel. I'm using the vesa driver, not fglrx. The computer goes to sleep fine, but when I hit the power button to resume, the fan comes back on, but the display stays off and the sleep light stays on. This works fine with both the Feisty and Hardy kernels.

It's kind of a pain to debug, because I have to power cycle the machine when it doesn't resume, but I can help debug this problem further if that means we get a working kernel. Thanks for looking at this; the suspend feature is crucial for anyone who actually uses Linux on a laptop.

Revision history for this message
Tobias McNulty (tmcnulty1982) wrote :

Suspend is also broken using fglrx with the 2.6.22 kernel. However, fglrx works with the 2.6.20 kernel. I don't expect this comes as a surprise to anyone, but I thought I'd mention that it is indeed still the case. On a side note, what is the problem with this? I thought ATI release the source code for their driver? Thanks, Tobias

Revision history for this message
Nanley Chery (nanoman) wrote :

I am assigning this bug to the 'ubuntu-kernel-acpi' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-acpi
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
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 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

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