Description of problem: When attempting to suspend the system, it resumes immediately Version-Release number of selected component (if applicable): All 3.2 kernels it seems including kernel-3.2.2-1.fc16.i686 kernel-3.2.3-2.fc16.i686 kernel-3.2.5-3.fc16.i686 - previous 3.x kernels have suspended and resumed reliably How reproducible: 100% Steps to Reproduce: 1.suspend through lid action or pm-suspend as root 2.observe instantaneous resume 3. Actual results: instant resume Expected results: suspend until lid open or key input Additional info: Hardware is HP Mini 311c model name : Intel(R) Atom(TM) CPU N270 @ 1.60GHz 00:16.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1) 02:00.0 VGA compatible controller: nVidia Corporation ION LE VGA (rev b1) 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) This worked with previous 3.x kernels, I'm not sure what point the change happened at but I went back and tried all installed kernels and they showed the same behaviour. I am running initrdless and have nouveau graphics. The log from a suspend / resume shows nothing strange apart from the instant resume: Feb 12 12:08:12 bishop kernel: [ 76.348482] PM: late suspend of devices comple te after 66.697 msecs Feb 12 12:08:12 bishop kernel: [ 76.348531] ACPI: Preparing to enter system sl eep state S3 Feb 12 12:08:12 bishop kernel: [ 76.373108] PM: Saving platform NVS memory Feb 12 12:08:12 bishop kernel: [ 76.375294] Disabling non-boot CPUs ... Feb 12 12:08:12 bishop kernel: [ 76.377063] CPU 1 is now offline Feb 12 12:08:12 bishop kernel: [ 76.377772] CPU 1 offline: Remove Rx thread Feb 12 12:08:12 bishop kernel: [ 76.378028] Extended CMOS year: 2000 Feb 12 12:08:12 bishop kernel: [ 76.378028] ACPI: Low-level resume complete Feb 12 12:08:12 bishop kernel: [ 76.378028] PM: Restoring platform NVS memory Feb 12 12:08:12 bishop kernel: [ 76.378028] Extended CMOS year: 2000 Feb 12 12:08:12 bishop kernel: [ 76.378028] microcode: CPU0 updated to revisio n 0x218, date = 2009-04-10 Feb 12 12:08:12 bishop kernel: [ 76.386477] Enabling non-boot CPUs ... Feb 12 12:08:12 bishop kernel: [ 76.386685] Booting Node 0 Processor 1 APIC 0x1 Feb 12 12:08:12 bishop kernel: [ 76.376808] Initializing CPU#1
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
No change whatsoever with the new kernel, see output below: /proc/cmdline: BOOT_IMAGE=/vmlinuz-3.3.0-4.fc16.i686 root=/dev/sda3 ro quiet rhgb rootfstype=ext4 plymouth.disable=0 pcie_aspm=force enforcing=0 [ 202.834796] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [ 202.846338] PM: Entering mem sleep [ 202.846490] Suspending console(s) (use no_console_suspend to debug) [ 202.854691] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 202.854819] sd 0:0:0:0: [sda] Stopping disk [ 202.876857] [drm] nouveau 0000:02:00.0: Disabling display... [ 203.971438] [drm] nouveau 0000:02:00.0: Disabling fbcon... [ 203.971477] [drm] nouveau 0000:02:00.0: Unpinning framebuffer(s)... [ 203.971597] [drm] nouveau 0000:02:00.0: Evicting buffers... [ 204.049805] [drm] nouveau 0000:02:00.0: Idling channels... [ 204.049996] [drm] nouveau 0000:02:00.0: Suspending GPU objects... [ 206.427569] [drm] nouveau 0000:02:00.0: And we're gone! [ 206.438833] nouveau 0000:02:00.0: power state changed by ACPI to D3 [ 206.439116] PM: suspend of devices complete after 3592.230 msecs [ 206.461269] ehci_hcd 0000:00:06.1: wake-up capability enabled by ACPI [ 206.472133] ohci_hcd 0000:00:06.0: wake-up capability enabled by ACPI [ 206.483217] ehci_hcd 0000:00:04.1: wake-up capability enabled by ACPI [ 206.494147] ohci_hcd 0000:00:04.0: wake-up capability enabled by ACPI [ 206.505496] PM: late suspend of devices complete after 66.360 msecs [ 206.505569] ACPI: Preparing to enter system sleep state S3 [ 206.530146] PM: Saving platform NVS memory [ 206.534627] Disabling non-boot CPUs ... [ 206.536885] CPU 1 is now offline [ 206.537975] CPU 1 offline: Remove Rx thread [ 206.538424] Extended CMOS year: 2000 [ 206.538424] ACPI: Low-level resume complete [ 206.538424] PM: Restoring platform NVS memory [ 206.538424] Extended CMOS year: 2000 [ 206.538424] microcode: CPU0 updated to revision 0x218, date = 2009-04-10 [ 206.546601] Enabling non-boot CPUs ... [ 206.547158] Booting Node 0 Processor 1 APIC 0x1 [ 206.547168] smpboot cpu 1: start_ip = 9b000 [ 206.536559] Initializing CPU#1 [ 206.536559] Disabled fast string operations [ 206.536559] Calibrating delay loop (skipped) already calibrated this CPU [ 206.559344] NMI watchdog enabled, takes one hw-pmu counter. [ 206.561485] microcode: CPU1 updated to revision 0x218, date = 2009-04-10 [ 206.570556] bnx2i: CPU 1 online: Create Rx thread [ 206.571195] CPU1 is up [ 206.573228] ACPI: Waking up from system sleep state S3 [ 206.582703] ohci_hcd 0000:00:04.0: wake-up capability disabled by ACPI [ 206.582857] ehci_hcd 0000:00:04.1: wake-up capability disabled by ACPI [ 206.582937] ohci_hcd 0000:00:06.0: wake-up capability disabled by ACPI [ 206.583116] ehci_hcd 0000:00:06.1: wake-up capability disabled by ACPI [ 206.595069] PM: early resume of devices complete after 12.910 msecs [ 206.595386] ohci_hcd 0000:00:04.0: setting latency timer to 64 [ 206.595538] ehci_hcd 0000:00:04.1: setting latency timer to 64 [ 206.595634] ohci_hcd 0000:00:06.0: setting latency timer to 64 [ 206.595654] ehci_hcd 0000:00:06.1: setting latency timer to 64 [ 206.595769] snd_hda_intel 0000:00:08.0: setting latency timer to 64 [ 206.595782] pci 0000:00:09.0: setting latency timer to 64 [ 206.596121] ahci 0000:00:0b.0: setting latency timer to 64 [ 206.596172] pci 0000:00:10.0: setting latency timer to 64 [ 206.596205] [drm] nouveau 0000:02:00.0: We're back, enabling device... [ 206.597970] nouveau 0000:02:00.0: power state changed by ACPI to D0 [ 206.597996] nouveau 0000:02:00.0: power state changed by ACPI to D0 [ 206.598060] nouveau 0000:02:00.0: power state changed by ACPI to D0 [ 206.598085] nouveau 0000:02:00.0: power state changed by ACPI to D0 [ 206.598129] nouveau 0000:02:00.0: setting latency timer to 64 [ 206.598146] [drm] nouveau 0000:02:00.0: POSTing device...
I am still troubled by this bug in spite of many kernel updates, so I thought I would backtrack to find a working kernel. I find that the latest kernels including: kernel-3.3.4-3.fc16.i686 kernel-3.3.5-2.fc16.i686 still have the problem. However an ancient kernel kernel-3.1.7-1.fc16.i686 suspends fine. Any tips on how to home in on the problem further (and maybe fix it?)
After much searching I found https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903399 Also #791149 which sounds like the same problem. If I disable wifi/bluetooth with the rf kill switch, suspend works.
After more experimentation I found that the rfkill can be triggered by software and the switch controls at least two settings - one for bluetooth and one for wifi. I found that disabling bluetooth from the command line or from the GUI is enough to make suspend work. Wifi has no bearing on the suspend issue. This is great news for me because I can live without bluetooth more easily than I can live without suspend. If anyone wants to look into this further I'd guess that changes to the way bluetooth suspends/resumes in linux 3.2 that are maybe specific to the driver that identifies itself as hp-bluetooth (hp-wmi maybe) are to blame for this instant resume bug.
Same behavior reproducible on ASUS EEE PC1201N. Turning bluetooth off from gui suffices to make suspend work. Kernel: 3.3.8-1.fc16.i686.PAE May be related to https://bugzilla.kernel.org/show_bug.cgi?id=43081
Are you still having issues with the 3.4 or 3.5 kernel updates?
Hello Josh, yes the symptoms are still the same in spite of many other things changing. I have installed the nvidia driver, which is far superior in terms of surviving suspend/resume. With nouveau I get occasional crashes after resume. I have also replaced the troublesome ath9k needing hardware with an intel a/b/g/n device which uses the iwlwifi driver. I still need pcie_aspm=force on the kernel command line to boot successfully. If I turn on bluetooth the suspend attempt resumes immediately. My netbook has a dedicated bluetooth device built in - I thought it was a part of the Atheros chipset for some reason. Removing the Atheros wireless h/w had no effect on the operation of the rf_kill feature and the bluetooth suspend/resume interference is exactly the same. If you need more info or testing please update the bug.
last failed on: 3.5.3-1.fc17.i686
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
I observe immediate resume after either suspend to RAM and suspend to disk on a Fedora 17 installation with kernel 3.6.2-4.fc17.x86_64 on an Asus M2N-MX SE Plus motherboard with a processor AMD Athlon(tm) 64 X2 Dual Core Processor 4400+, when an USB printer (Samsung ML2850D) is connected and on. If the printed is connected but off suspend works. I attach part of the log file. Oct 23 12:16:35 woland NetworkManager[628]: <info> sleep requested (sleeping: no enabled: yes) Oct 23 12:16:35 woland NetworkManager[628]: <info> sleeping or disabling... Oct 23 12:16:35 woland NetworkManager[628]: <info> (em1): now unmanaged Oct 23 12:16:35 woland NetworkManager[628]: <info> (em1): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Oct 23 12:16:35 woland NetworkManager[628]: <info> (em1): deactivating device (reason 'sleeping') [37] Oct 23 12:16:35 woland NetworkManager[628]: <info> (em1): canceled DHCP transaction, DHCP client pid 841 Oct 23 12:16:35 woland NetworkManager[628]: <info> (em1): cleaning up... Oct 23 12:16:35 woland NetworkManager[628]: <info> (em1): taking down device. Oct 23 12:16:35 woland avahi-daemon[668]: Withdrawing address record for 192.168.1.2 on em1. Oct 23 12:16:35 woland avahi-daemon[668]: Leaving mDNS multicast group on interface em1.IPv4 with address 192.168.1.2. Oct 23 12:16:35 woland avahi-daemon[668]: Interface em1.IPv4 no longer relevant for mDNS. Oct 23 12:16:35 woland avahi-daemon[668]: Withdrawing address record for fe80::21e:8cff:fe0a:9a2d on em1. Oct 23 12:16:35 woland dbus-daemon[696]: dbus[696]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Oct 23 12:16:35 woland dbus[696]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Oct 23 12:16:35 woland dbus-daemon[696]: dbus[696]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 23 12:16:35 woland dbus[696]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 23 12:16:36 woland iscsi[1717]: Stopping iscsi: [ OK ] Oct 23 12:16:36 woland dbus-daemon[696]: Stopping iscsi (via systemctl): [ OK ] Oct 23 12:16:36 woland kernel: [ 461.115748] ehci_hcd 0000:00:02.1: remove, state 4 Oct 23 12:16:36 woland kernel: [ 461.115769] usb usb1: USB disconnect, device number 1 Oct 23 12:16:36 woland kernel: [ 461.117552] ehci_hcd 0000:00:02.1: USB bus 1 deregistered Oct 23 12:16:36 woland ntpd[651]: Deleting interface #5 em1, fe80::21e:8cff:fe0a:9a2d#123, interface stats: received=0, sent=0, dropped=0, active_time=428 secs Oct 23 12:16:36 woland ntpd[651]: Deleting interface #4 em1, 192.168.1.2#123, interface stats: received=54, sent=54, dropped=0, active_time=430 secs Oct 23 12:16:36 woland ntpd[651]: 217.194.13.90 interface 192.168.1.2 -> (none) Oct 23 12:16:36 woland ntpd[651]: 2.228.72.62 interface 192.168.1.2 -> (none) Oct 23 12:16:36 woland ntpd[651]: 212.45.144.88 interface 192.168.1.2 -> (none) Oct 23 12:16:36 woland ntpd[651]: 212.121.88.250 interface 192.168.1.2 -> (none) Oct 23 12:16:36 woland ntpd[651]: peers refreshed Oct 23 13:29:19 woland kernel: [ 462.060992] PM: Syncing filesystems ... done. Oct 23 13:29:19 woland kernel: [ 462.064820] Freezing user space processes ... (elapsed 0.01 seconds) done. Oct 23 13:29:19 woland kernel: [ 462.076090] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Oct 23 13:29:19 woland kernel: [ 462.087109] Suspending console(s) (use no_console_suspend to debug) Oct 23 13:29:19 woland kernel: [ 462.087358] sd 3:0:0:0: [sdb] Synchronizing SCSI cache Oct 23 13:29:19 woland kernel: [ 462.087557] sd 2:0:0:0: [sda] Synchronizing SCSI cache Oct 23 13:29:19 woland kernel: [ 462.087721] sd 2:0:0:0: [sda] Stopping disk Oct 23 13:29:19 woland kernel: [ 462.107869] serial 00:0c: disabled Oct 23 13:29:19 woland kernel: [ 462.107876] serial 00:0c: wake-up capability disabled by ACPI Oct 23 13:29:19 woland kernel: [ 462.107893] i8042 aux 00:0a: wake-up capability disabled by ACPI Oct 23 13:29:19 woland kernel: [ 462.107908] i8042 kbd 00:09: wake-up capability enabled by ACPI Oct 23 13:29:19 woland kernel: [ 462.108241] parport_pc 00:06: disabled Oct 23 13:29:19 woland kernel: [ 462.170116] sd 3:0:0:0: [sdb] Stopping disk Oct 23 13:29:19 woland kernel: [ 462.851085] PM: suspend of devices complete after 763.802 msecs Oct 23 13:29:19 woland kernel: [ 462.851231] PM: late suspend of devices complete after 0.143 msecs Oct 23 13:29:19 woland kernel: [ 462.862074] ohci_hcd 0000:00:02.0: wake-up capability enabled by ACPI Oct 23 13:29:19 woland kernel: [ 462.873104] PM: noirq suspend of devices complete after 21.869 msecs Oct 23 13:29:19 woland kernel: [ 462.873183] ACPI: Preparing to enter system sleep state S3 Oct 23 13:29:19 woland kernel: [ 462.874372] PM: Saving platform NVS memory Oct 23 13:29:19 woland kernel: [ 462.874597] Disabling non-boot CPUs ... Oct 23 13:29:19 woland kernel: [ 462.875922] smpboot: CPU 1 is now offline Oct 23 13:29:19 woland kernel: [ 462.876397] CPU 1 offline: Remove Rx thread Oct 23 13:29:19 woland kernel: [ 462.876532] Extended CMOS year: 2000 Oct 23 13:29:19 woland kernel: [ 462.876532] ACPI: Low-level resume complete Oct 23 13:29:19 woland kernel: [ 462.876532] PM: Restoring platform NVS memory Oct 23 13:29:19 woland kernel: [ 462.876532] Extended CMOS year: 2000 Oct 23 13:29:19 woland kernel: [ 462.877302] Enabling non-boot CPUs ... Oct 23 13:29:19 woland kernel: [ 462.877449] smpboot: Booting Node 0 Processor 1 APIC 0x1 Oct 23 13:29:19 woland kernel: [ 462.889634] bnx2i: CPU 1 online: Create Rx thread Oct 23 13:29:19 woland kernel: [ 462.889683] CPU1 is up Oct 23 13:29:19 woland kernel: [ 462.890133] ACPI: Waking up from system sleep state S3 Oct 23 13:29:19 woland kernel: [ 462.912059] ohci_hcd 0000:00:02.0: wake-up capability disabled by ACPI Oct 23 13:29:19 woland kernel: [ 462.912138] pci 0000:00:00.0: Found enabled HT MSI Mapping Oct 23 13:29:19 woland kernel: [ 462.934094] pci 0000:00:00.0: Found enabled HT MSI Mapping Oct 23 13:29:19 woland kernel: [ 462.945079] pci 0000:00:00.0: Found enabled HT MSI Mapping Oct 23 13:29:19 woland kernel: [ 462.945150] pci 0000:00:00.0: Found enabled HT MSI Mapping Oct 23 13:29:19 woland kernel: [ 462.945222] pci 0000:00:00.0: Found enabled HT MSI Mapping Oct 23 13:29:19 woland kernel: [ 462.945298] pci 0000:00:00.0: Found enabled HT MSI Mapping Oct 23 13:29:19 woland kernel: [ 462.956138] PM: noirq resume of devices complete after 64.703 msecs Oct 23 13:29:19 woland kernel: [ 462.956253] PM: early resume of devices complete after 0.070 msecs Oct 23 13:29:19 woland kernel: [ 462.969344] parport_pc 00:06: activated Oct 23 13:29:19 woland kernel: [ 462.969366] i8042 kbd 00:09: wake-up capability disabled by ACPI Oct 23 13:29:19 woland kernel: [ 462.970480] serial 00:0c: activated Oct 23 13:29:19 woland kernel: [ 463.018309] Extended CMOS year: 2000 Oct 23 13:29:19 woland kernel: [ 463.126579] ata1.01: ACPI cmd ef/03:42:00:00:00:b0 (SET FEATURES) filtered out Oct 23 13:29:19 woland kernel: [ 463.126581] ata1.01: ACPI cmd ef/03:01:00:00:00:b0 (SET FEATURES) filtered out Oct 23 13:29:19 woland kernel: [ 463.126584] ata1.01: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Oct 23 13:29:19 woland kernel: [ 463.129599] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES) filtered out Oct 23 13:29:19 woland kernel: [ 463.129601] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Oct 23 13:29:19 woland kernel: [ 463.135555] ata1.00: configured for UDMA/66 Oct 23 13:29:19 woland kernel: [ 463.141484] ata1.01: configured for UDMA/33 Oct 23 13:29:19 woland kernel: [ 466.078050] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Oct 23 13:29:19 woland kernel: [ 466.154174] ata3.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out Oct 23 13:29:19 woland kernel: [ 466.154177] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Oct 23 13:29:19 woland kernel: [ 466.160288] ata3.00: configured for UDMA/133 Oct 23 13:29:19 woland kernel: [ 466.160335] sd 2:0:0:0: [sda] Starting disk Oct 23 13:29:19 woland kernel: [ 468.476022] ata4: link is slow to respond, please be patient (ready=0) Oct 23 13:29:19 woland kernel: [ 468.986081] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 23 13:29:19 woland kernel: [ 468.989155] ata4.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out Oct 23 13:29:19 woland kernel: [ 468.989157] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Oct 23 13:29:19 woland kernel: [ 469.020307] ata4.00: configured for UDMA/133 Oct 23 13:29:19 woland kernel: [ 469.031050] sd 3:0:0:0: [sdb] Starting disk Oct 23 13:29:19 woland kernel: [ 469.040909] PM: resume of devices complete after 6084.651 msecs Oct 23 13:29:19 woland kernel: [ 469.041105] Restarting tasks ... done.
As per comment 10, many changes but still the same buggy behaviour. If bluetooth is disabled then suspend is successful. Fedora release 17 (Beefy Miracle) kernel-3.6.2-4.fc17.i686
I had this on Fedora release 17 (Beefy Miracle) on an ASUS laptop. The workaround that exists in the current Fedora, in /etc/pm/sleep.d/20-custom-ehci_hcd, breaks on this system because that device doesn't exist. I needed to change the device to ehci-pci instead of ehci_hcd, then suspend works again.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.