[1.] One line summary of the problem: --- Ubuntu 12.04 does not suspend [2.] Full description of the problem/report: 1- I click supend, it attempts to suspend and shuts off with the power button blinking-as it does normally when it suspended(worked in 9.04). 2-however when it comes out of suspend it simply reboots- as in displays the "vaio" logo then goes to bootloader and waits for my input. It then boots from hdd-hd activity light on for 10-15 seconds and it eventually boots to login screen. The outcome is the same whether i close the lid, click the suspend button or run sudo pm-suspend . [3.] Keywords (i.e., modules, networking, kernel): [4.] Kernel version (from /proc/version): [7.] Environment [7.1.] Software (add the output of the ver_linux script here) [7.2.] Processor information (from /proc/cpuinfo): [7.3.] Module information (from /proc/modules): [7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem) [7.5.] PCI information ('lspci -vvv' as root)---see lspci vvv file [7.6.] SCSI information (from /proc/scsi/scsi) When creating your bug report be sure to _attach_ any relevant information. This will usually include: the version of the kernel you are running (uname -r)----anton@anton-VGN-NW11S-T:~$ uname -r 3.2.0-24-generic-pae dmesg output.--- see attached file. ---Also see bootdmesg.txt lspci -vvnn output.--see attached file lspci output If the bug is about interrupts, then /proc/interrupts is also helpful. If a BIOS issue is suspected, dmidecode output is also helpful. If the bug is regarding memory oddities, /proc/mtrr info is also helpful. Most importantly, if this is a regression, the best information you can provide the kernel developers is the information from doing a git bisect. This will hopefully narrow down the exact patch that is causing the regression. The following link will help you through this process. This is related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995052 Bug #995052 Please find attached all the previously described files in a tar.gz container
Created attachment 73230 [details] bootDmesg output
Created attachment 73231 [details] dmesg on 9th of may
Created attachment 73232 [details] dmidecode output
Created attachment 73233 [details] lspci output
Created attachment 73234 [details] lspci vvv output
Created attachment 73235 [details] scsi output
If I can provide any other information (or test the fixes ) i am very happy to do so :-)
Can you attach the output of /proc/acpi/wakeup?
Created attachment 73301 [details] file of /proc..
Can you disable USBx, EHC1 and EHC2 wakeup? text again. e.g disable USB0 wakeup. echo USB0 > /proc/acpi/wakeup Device S-state Status Sysfs node USB0 S3 *enabled pci:0000:00:1d.0 USB1 S3 *enabled pci:0000:00:1d.1 USB2 S3 *enabled pci:0000:00:1d.2 USBR S3 *disabled EHC1 S3 *enabled pci:0000:00:1d.7 USB3 S3 *enabled pci:0000:00:1a.0 USB4 S3 *enabled pci:0000:00:1a.1 USB5 S3 *enabled pci:0000:00:1a.2 EHC2 S3 *enabled pci:0000:00:1a.7 RP01 S3 *disabled pci:0000:00:1c.0 PXSX S3 *disabled pci:0000:02:00.0 RP02 S3 *disabled pci:0000:00:1c.1 PXSX S3 *disabled pci:0000:03:00.0 RP03 S3 *disabled pci:0000:00:1c.2 PXSX S3 *disabled PXSX S3 *disabled PXSX S3 *disabled PXSX S3 *disabled PWRB S4 *enabled
anton@anton-VGN-NW11S-T:~$ sudo gedit /proc/acpi/wakeup [sudo] password for anton: anton@anton-VGN-NW11S-T:~$ echo [USb,EHC etc] > /proc/acpi/wakeup gets me the following: Device S-state Status Sysfs node USB0 S3 *disabled pci:0000:00:1d.0 USB1 S3 *disabled pci:0000:00:1d.1 USB2 S3 *disabled pci:0000:00:1d.2 USBR S3 *disabled EHC1 S3 *disabled pci:0000:00:1d.7 USB3 S3 *disabled pci:0000:00:1a.0 USB4 S3 *disabled pci:0000:00:1a.1 USB5 S3 *disabled pci:0000:00:1a.2 EHC2 S3 *disabled pci:0000:00:1a.7 RP01 S3 *disabled pci:0000:00:1c.0 PXSX S3 *disabled pci:0000:02:00.0 RP02 S3 *disabled pci:0000:00:1c.1 PXSX S3 *disabled pci:0000:03:00.0 RP03 S3 *disabled pci:0000:00:1c.2 PXSX S3 *disabled PXSX S3 *disabled PXSX S3 *disabled PXSX S3 *disabled PWRB S4 *enabled
The machine still rebooted when suspended?
I have not yet tried--are the changes saved to the above file??? Ill try now and see if it did.
Have just tried to suspend and it still rebooted. have just done sudo nano /proc/acpi/wakeup and it returned this: Device S-state Status Sysfs node USB0 S3 *enabled pci:0000:00:1d.0 USB1 S3 *enabled pci:0000:00:1d.1 USB2 S3 *enabled pci:0000:00:1d.2 USBR S3 *disabled EHC1 S3 *enabled pci:0000:00:1d.7 USB3 S3 *enabled pci:0000:00:1a.0 USB4 S3 *enabled pci:0000:00:1a.1 USB5 S3 *enabled pci:0000:00:1a.2 EHC2 S3 *enabled pci:0000:00:1a.7 RP01 S3 *disabled pci:0000:00:1c.0 PXSX S3 *disabled pci:0000:02:00.0 RP02 S3 *disabled pci:0000:00:1c.1 PXSX S3 *disabled pci:0000:03:00.0 RP03 S3 *disabled pci:0000:00:1c.2 PXSX S3 *disabled PXSX S3 *disabled PXSX S3 *disabled PXSX S3 *disabled Have my settings not been saved???
This is runtime setting and will not be saved. Please follow steps in the linux tree/Documentation/power/basic-pm-debugging.txt to debug.
(linux kernel tree)/Documentation/power/basic-pm-debugging.txt
Ok- I have tried to debug the issue but ended up reinstalling with the canonical dvd that came throught the post. The hibernate feature works very well using s2disk =happy . Suspend still does not work as apparently my computer is not recognized. I am happy that at least hibernate works so i can save my machines state.
Hi: Does this issue for suspend still exist in the latest upstream kernel? Have you debuged according basic-pm-debugging.txt for suspend?
On Dec 12, 2012 6:41 AM, <bugzilla-daemon@bugzilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=43220 > Hi Lan, > Nope, just tried 3.7 rc8 raring, suspend works, resumes normally,seems like the bug is fixed. > > > > > --- Comment #18 from Lan Tianyu <tianyu.lan@intel.com> 2012-12-12 > 06:40:59 --- > Hi: > Does this issue for suspend still exist in the latest upstream > kernel? > Have you debuged according basic-pm-debugging.txt for suspend? > > -- > Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > You reported the bug. >
That's Great. Close the bug.