Suspend stops working if ATI restricted driver is enabled

Bug #152463 reported by Rajamani Saravanan
8
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

Machine: Acer Ferrari AMD64, 1.5GB RAM, 120 GB harddisk
OS: Gutsy beta

I have Feisty and Gutsy on the same machine on different partitions, suspend/resume has been working perfectly fine for me with Feisty even when the ATI restricted drivers are enabled (enabling the driver is required for stability).

I did a Gutsy beta install, tried suspend/resume with the default display driver, worked fine. But after enabling the ATI restricted driver, suspend/resume stops working.. (after initiating a suspend, screen blanks but the machine doesnt 'power down', it continues running, but no action can bring it back to life.. ..you have to force shutdown and bring it up again). Disabling the ATI driver makes suspend/resume work again correctly.

Revision history for this message
Raul Acuña (reacuna) wrote :

I can confirm this, on a Acer Ferrari 4005Wlmi, using xserver-xgl and the ATI restricted driver.

Revision history for this message
Joerg Delker (ubuntu-delker) wrote :

After upgrading to Gutsy, suspend/resume (ram & disk) does NOT work anymore on my Acer Ferrari 4005.

Currently, I can't see a relation to the ATI restricted drivers, because I tested without the drivers in init=/bin/sh state and have very similar behavior:

I'm initiating suspend with "s2both". The machine displays suspend information and finally shuts down (power led blinking orange).
Pressing any key after that DOES awake the system, but screen remains blank. However, as HDD LED indicates the OS has been revived and a CTRL-ALT-DEL does shutdown/reboot eventually.

Conclusion: I suspect not the ATI drivers being source of the problem but a general (kernel) problem!?
As already mentioned, this worked perfectly with Feisty, so something must have changed with the Update which broke suspend/resume on this platform.

This is with linux-image-2.6.22-14-generic.

Any clues welcome.

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
mmlb (mmlb) wrote :

Ok So I too am having this problem and I am attaching the files asked for from the debuggingacpi from the wiki. I checked out the kernel log and theres nothing from today. Also dont know if its any good but after clicking suspend screen turned off like normal and so did the "disk usage" LED, but neither the Power button LED or the Bluetooth LED turned off and the what I call "system status" LED did not turn orange to indicate asleep.

Revision history for this message
mmlb (mmlb) wrote :
Revision history for this message
mmlb (mmlb) wrote :
Revision history for this message
mmlb (mmlb) wrote :
Revision history for this message
mmlb (mmlb) wrote :
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
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
Rajamani Saravanan (rajamani-saravanan) wrote : Re: [Bug 152463] Re: Suspend stops working if ATI restricted driver is enabled

Thanks, Nanley. Rgds, RS.

On 12/13/07, Nanley Chery <email address hidden> 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 (Ubuntu)
> Assignee: (unassigned) => Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi)
>
> --
> Suspend stops working if ATI restricted driver is enabled
> https://bugs.launchpad.net/bugs/152463
> You received this bug notification because you are a direct subscriber
> of the bug.
>

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.