Additional info: WARNING: at kernel/power/suspend_test.c:53 suspend_test_finish+0x8c/0x90() Hardware name: 251676C Component: suspend devices, time: 11392 Modules linked in: ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc fuse ebtable_nat nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_nat nf_nat_ipv6 ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack bnep bluetooth nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_intel snd_hda_codec arc4 snd_hwdep iwldvm mac80211 snd_seq uvcvideo videobuf2_vmalloc e1000e iwlwifi videobuf2_memops videobuf2_core snd_seq_device videodev media acpi_cpufreq sdhci_pci snd_pcm thinkpad_acpi snd_page_alloc cfg80211 sdhci ptp iTCO_wdt snd_timer mperf coretemp mmc_core pps_core iTCO_vendor_support snd lpc_ich mfd_core rfkill soundcore i2c_i801 mei microcode nouveau i2c_algo_bit firewire_ohci mxm_wmi drm_kms_helper firewire_core crc_itu_t ttm drm i2c_core wmi video uinput Pid: 17762, comm: systemd-sleep Not tainted 3.9.0-0.rc4.git0.1.fc20.i686.PAE #1 Call Trace: [<c045573c>] warn_slowpath_common+0x6c/0xa0 [<c04a8a8c>] ? suspend_test_finish+0x8c/0x90 [<c04a8a8c>] ? suspend_test_finish+0x8c/0x90 [<c04557a3>] warn_slowpath_fmt+0x33/0x40 [<c04a8a8c>] suspend_test_finish+0x8c/0x90 [<c04a8268>] suspend_devices_and_enter+0x78/0x5b0 [<c04a8906>] pm_suspend+0x166/0x240 [<c04a76db>] state_store+0x5b/0xb0 [<c04a7680>] ? pm_trace_dev_match_show+0x20/0x20 [<c06e11f7>] kobj_attr_store+0x17/0x30 [<c05f6233>] sysfs_write_file+0xa3/0x110 [<c05f6190>] ? sysfs_remove_files+0x30/0x30 [<c058afa2>] vfs_write+0x82/0x150 [<c058b131>] sys_write+0x41/0x80 [<c0a5714d>] sysenter_do_call+0x12/0x38 Potential duplicate: bug 860215
Created attachment 716857 [details] File: dmesg
The reason you're seeing this warning is that the suspend test took longer than 10 seconds (which is a lifetime) to complete. [ 5867.060791] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 5867.075006] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [ 5867.087224] PM: Entering mem sleep [ 5867.087997] Suspending console(s) (use no_console_suspend to debug) [ 5867.093192] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 5867.155616] sd 0:0:0:0: [sda] Stopping disk [ 5867.310697] nouveau [ DRM] suspending fbcon... [ 5867.310814] nouveau [ DRM] suspending display... [ 5867.310958] nouveau [ DRM] unpinning framebuffer(s)... [ 5867.311897] nouveau [ DRM] evicting buffers... [ 5871.539847] nouveau [ DRM] suspending client object trees... [ 5878.480497] nouveau 0000:01:00.0: power state changed by ACPI to D3hot ^^^ the nouveau driver took a long time to suspend for some reason. [ 5878.480748] PM: suspend of devices complete after 11388.678 msecs [ 5878.480752] PM: suspend devices took 11.392 seconds ^^^ and the whole suspend took 11 seconds, which causes the warning below: [ 5878.480754] ------------[ cut here ]------------ [ 5878.480765] WARNING: at kernel/power/suspend_test.c:53 suspend_test_finish+0x8c/0x90() [ 5878.480767] Hardware name: 251676C <snip> OOC, what type of hardware is this? P.
I have to say suspend tasks are still long. But now my kernel is 3.10 so I don't know how to provide more information to you. My hardware is Lenovo T410i 251676C with Intel Pentium P6000 and NVS 3100m
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.