Gutsy suspend to RAM fails on ACER Veriton 5500

[Craigus]

Binary package hint: linux-source-2.6.22

Suspend works perfectly under Feisty on this hardware. I have up-to-date Gutsy installed. Suspend to RAM has not worked under any version of Gutsy (I started with Tribe 3). The screen blanks, monitor goes to standby, but the machine stays fully powered with fans running and power lights on. No response to anything other than CRTl-ALT-DEL, which does reboot the machine.

Issuing "/etc/acpi/sleep.sh force" results in this same behaviour as does pressing the keyboard sleep button or selecting suspend in the GUI.

The machine has a Matrox G200 card for the secondary monitor; primary is the inbuilt Intel video, using the current intel driver (not the i810 one).

"uname -a" : Linux xxx-desktop-ubuntu 2.6.22-11-generic #1 SMP Fri Sep 7 05:07:05 GMT 2007 i686 GNU/Linux

I have attempted to follow the procedure: : https://wiki.ubuntu.com/DebuggingKernelSuspend , however the machine will not suspend correctly, so I am unsure what to do next.

[Brian Murray (brian-murray)]

While not pertinent to this bug report you might want to look into this from you dmesg file:

[ 24.473418] attempt to access beyond end of device
[ 24.473422] sdb2: rw=16, want=8, limit=2
[ 24.473426] Read-error on swap-device (8:18:8)

[Craigus (craigusoz)]

Just updating here - the issue still occurs with Gutsy final; identical symptoms.

[Brian Murray (brian-murray)]

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 https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in .

[Bob Stockdale (stocks29)]

I am having the exact same problem. Only difference is that I have an Nvidia 7900GT graphics card, not a matrox.

[Launchpad Janitor (janitor)]

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!

[Leann Ogasawara (leannogasawara)]

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.

[Leann Ogasawara (leannogasawara)]

*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".