Bug 794525

Summary: 3.2.6-3.fc16.x86_64 doesnt suspend
Product: [Fedora] Fedora Reporter: Mohammed Arafa <bugzilla>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: fb.commerce, gansalmon, itamar, jhparizona, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: suspend first=3.2 tested=3.5.3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-02 18:21:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Output of the command ' lsmod >lsmod.txt' none

Description Mohammed Arafa 2012-02-17 02:23:06 UTC 
Description of problem:
i updated my system yesterday to kernel 3.2.6-3.fc16.x86_64 and now when i shut the lid it doesnt suspend. although i am using kde there was no update yesterday when i noticed the issue.
my notebook is a lenovo t420

Version-Release number of selected component (if applicable):
3.2.6-3.fc16.x86_64

How reproducible:
everytime

Steps to Reproduce:
1.upgrade to kernel 3.2.6-3.fc16.x86_64
2.shut notebook lid
3.
  
Actual results:
no suspend action

Expected results:
laptop suspends

Additional info:
i7 processor ?
Comment 1 Ferdinand Badescu 2012-02-23 02:57:21 UTC 
Ditto on a AMD 64-bit desktop: Issuing the suspend command (either from within a GUI -Gnome 3, or terminal -tty3, for example) yields the same result: the machine initiates the suspend mode all the way to suspending the hard disc, then it wakes up by itself. If the command is repeated two-three times it results in the graphics card entering a suspend mode without a possibility to wake it up. The only way to come out of this predicament is to hard-reboot the computer.

I copied below two snippets from the stout: 1) /var/log/messages, related to the acpi process; 2) /var/log/pm-suspend.log (pm-powersave.log file is empty):

1)
"Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> sleep requested (sleeping: no  enabled: yes)
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> sleep requested (sleeping: no  enabled: yes)
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> sleeping or disabling...
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (wlan0): now unmanaged
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (wlan0): deactivating device (reason 'sleeping') [37]
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> sleeping or disabling...
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): now unmanaged
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): deactivating device (reason 'sleeping') [37]
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1146
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1146
Feb 22 18:10:32 cessna182 avahi-daemon[835]: Withdrawing address record for 192.168.1.133 on wlan0.
Feb 22 18:10:32 cessna182 avahi-daemon[835]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.133.
Feb 22 18:10:32 cessna182 avahi-daemon[835]: Interface wlan0.IPv4 no longer relevant for mDNS.
Feb 22 18:10:32 cessna182 kernel: [   74.090593] cfg80211: Calling CRDA to update world regulatory domain
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): cleaning up...
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (wlan0): cleaning up...
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): taking down device.
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (wlan0): taking down device.
Feb 22 18:10:32 cessna182 avahi-daemon[835]: Withdrawing address record for fe80::221:29ff:fe69:57eb on wlan0.
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (eth0): now unmanaged
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (eth0): now unmanaged
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (eth0): cleaning up...
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (eth0): cleaning up...
Feb 22 18:10:32 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (eth0): taking down device.
Feb 22 18:10:32 cessna182 NetworkManager[819]: <info> (eth0): taking down device.
Feb 22 18:10:32 cessna182 dbus-daemon[860]: dbus[860]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb 22 18:10:32 cessna182 dbus[860]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb 22 18:10:32 cessna182 kernel: [   74.171447] cfg80211: World regulatory domain updated:
Feb 22 18:10:32 cessna182 kernel: [   74.171451] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 22 18:10:32 cessna182 kernel: [   74.171455] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.171458] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.171461] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.171464] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.171466] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.171486] cfg80211: Calling CRDA for country: US
Feb 22 18:10:32 cessna182 kernel: [   74.197466] cfg80211: Regulatory domain changed to country: US
Feb 22 18:10:32 cessna182 kernel: [   74.197470] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 22 18:10:32 cessna182 kernel: [   74.197473] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.197476] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.197479] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.197482] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.197485] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 22 18:10:32 cessna182 kernel: [   74.197487] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Feb 22 18:10:32 cessna182 dbus-daemon[860]: dbus[860]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 22 18:10:32 cessna182 dbus[860]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 22 18:10:33 cessna182 systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Feb 22 18:10:33 cessna182 chronyd[894]: Source 64.113.32.5 offline
Feb 22 18:10:33 cessna182 chronyd[894]: Source 72.14.189.114 offline
Feb 22 18:10:33 cessna182 chronyd[894]: Source 64.16.211.38 offline
Feb 22 18:10:33 cessna182 chronyd[894]: Source 46.166.138.172 offline
Feb 22 18:10:33 cessna182 chronyd[894]: Source 192.43.244.18 offline
Feb 22 18:10:33 cessna182 systemd[1]: PID 1689 read from file /run/sm-client.pid does not exist.
Feb 22 18:10:44 cessna182 kernel: [   77.307800] PM: Syncing filesystems ... done.
Feb 22 18:10:44 cessna182 kernel: [   77.310214] Freezing user space processes ... (elapsed 0.01 seconds) done.
Feb 22 18:10:44 cessna182 kernel: [   77.321071] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Feb 22 18:10:44 cessna182 kernel: [   77.332081] Suspending console(s) (use no_console_suspend to debug)
Feb 22 18:10:44 cessna182 kernel: [   77.332332] sd 2:0:0:0: [sda] Synchronizing SCSI cache
Feb 22 18:10:44 cessna182 kernel: [   77.333139] serial 00:09: disabled
Feb 22 18:10:44 cessna182 kernel: [   77.333146] serial 00:09: wake-up capability disabled by ACPI
Feb 22 18:10:44 cessna182 kernel: [   77.333342] parport_pc 00:06: disabled
Feb 22 18:10:44 cessna182 kernel: [   77.345072] ohci_hcd 0000:00:0b.0: PCI INT A disabled
Feb 22 18:10:44 cessna182 kernel: [   77.385033] ehci_hcd 0000:00:0b.1: PCI INT B disabled
Feb 22 18:10:44 cessna182 kernel: [   77.484057] snd_hda_intel 0000:00:10.1: PCI INT B disabled
Feb 22 18:10:44 cessna182 kernel: [   77.726114] sd 2:0:0:0: [sda] Stopping disk
Feb 22 18:10:44 cessna182 kernel: [   78.433024] phy0 -> rt61pci_set_device_state: Error - Device failed to enter state 1 (-16).
Feb 22 18:10:44 cessna182 kernel: [   78.433048] rt61pci 0000:04:08.0: PCI INT A disabled
Feb 22 18:10:44 cessna182 kernel: [   78.537261] sata_nv 0000:00:0e.0: PCI INT A disabled
Feb 22 18:10:44 cessna182 kernel: [   78.548037] PM: suspend of devices complete after 1215.820 msecs
Feb 22 18:10:44 cessna182 kernel: [   78.559066] ehci_hcd 0000:00:0b.1: wake-up capability enabled by ACPI
Feb 22 18:10:44 cessna182 kernel: [   78.570047] ohci_hcd 0000:00:0b.0: wake-up capability enabled by ACPI
Feb 22 18:10:44 cessna182 kernel: [   78.581179] PM: late suspend of devices complete after 33.137 msecs
Feb 22 18:10:44 cessna182 kernel: [   78.581241] ACPI: Preparing to enter system sleep state S3
Feb 22 18:10:44 cessna182 kernel: [   78.581548] PM: Saving platform NVS memory
Feb 22 18:10:44 cessna182 kernel: [   78.581793] Disabling non-boot CPUs ...
Feb 22 18:10:44 cessna182 kernel: [   78.581829] Extended CMOS year: 2000
Feb 22 18:10:44 cessna182 kernel: [   78.581829] ACPI: Low-level resume complete
Feb 22 18:10:44 cessna182 kernel: [   78.581829] PM: Restoring platform NVS memory
Feb 22 18:10:44 cessna182 kernel: [   78.581829] Extended CMOS year: 2000
Feb 22 18:10:44 cessna182 kernel: [   78.582801] ACPI: Waking up from system sleep state S3
Feb 22 18:10:44 cessna182 kernel: [   78.583067] pci 0000:00:00.0: Found disabled HT MSI Mapping
Feb 22 18:10:44 cessna182 kernel: [   78.583072] pci 0000:00:00.0: Enabling HT MSI Mapping
Feb 22 18:10:44 cessna182 kernel: [   78.583268] pci 0000:00:00.0: Found enabled HT MSI Mapping
Feb 22 18:10:44 cessna182 kernel: [   78.583310] pci 0000:00:00.0: Found enabled HT MSI Mapping
Feb 22 18:10:44 cessna182 kernel: [   78.583355] pci 0000:00:00.0: Found enabled HT MSI Mapping
Feb 22 18:10:44 cessna182 kernel: [   78.583519] ohci_hcd 0000:00:0b.0: wake-up capability disabled by ACPI
Feb 22 18:10:44 cessna182 kernel: [   78.583555] ehci_hcd 0000:00:0b.1: wake-up capability disabled by ACPI
Feb 22 18:10:44 cessna182 kernel: [   78.583643] pci 0000:00:09.0: Found enabled HT MSI Mapping
Feb 22 18:10:44 cessna182 kernel: [   78.583708] pci 0000:00:09.0: Found enabled HT MSI Mapping
Feb 22 18:10:44 cessna182 kernel: [   78.583785] pci 0000:00:09.0: Found enabled HT MSI Mapping
Feb 22 18:10:44 cessna182 kernel: [   78.583966] PM: early resume of devices complete after 0.950 msecs
Feb 22 18:10:44 cessna182 kernel: [   78.584113] ohci_hcd 0000:00:0b.0: PCI INT A -> Link[LUB0] -> GSI 22 (level, low) -> IRQ 22
Feb 22 18:10:44 cessna182 kernel: [   78.584139] ehci_hcd 0000:00:0b.1: PCI INT B -> Link[LUB2] -> GSI 23 (level, low) -> IRQ 23
Feb 22 18:10:44 cessna182 kernel: [   78.584179] sata_nv 0000:00:0e.0: PCI INT A -> Link[LSA0] -> GSI 21 (level, low) -> IRQ 21
Feb 22 18:10:44 cessna182 kernel: [   78.584204] snd_hda_intel 0000:00:10.1: PCI INT B -> Link[LAZA] -> GSI 23 (level, low) -> IRQ 23
Feb 22 18:10:44 cessna182 kernel: [   78.657634] parport_pc 00:06: activated
Feb 22 18:10:44 cessna182 kernel: [   78.661040] serial 00:09: activated
Feb 22 18:10:44 cessna182 kernel: [   78.667072] sd 2:0:0:0: [sda] Starting disk
Feb 22 18:10:44 cessna182 kernel: [   79.028115] rt61pci 0000:04:08.0: PCI INT A -> Link[LNKA] -> GSI 19 (level, low) -> IRQ 19
Feb 22 18:10:44 cessna182 kernel: [   79.296035] usb 2-4: reset full-speed USB device number 2 using ohci_hcd
Feb 22 18:10:44 cessna182 kernel: [   79.458339] ata1.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out
Feb 22 18:10:44 cessna182 kernel: [   79.464284] ata1.00: configured for UDMA/33
Feb 22 18:10:44 cessna182 kernel: [   79.547026] ata4: SATA link down (SStatus 0 SControl 300)
Feb 22 18:10:44 cessna182 kernel: [   79.571021] usb 1-3: reset high-speed USB device number 2 using ehci_hcd
Feb 22 18:10:44 cessna182 kernel: [   79.825823] snd-usb-audio 1-3:1.2: no reset_resume for driver snd-usb-audio?
Feb 22 18:10:44 cessna182 kernel: [   79.825826] snd-usb-audio 1-3:1.3: no reset_resume for driver snd-usb-audio?
Feb 22 18:10:44 cessna182 kernel: [   82.289034] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 22 18:10:44 cessna182 kernel: [   83.182183] ata3.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
Feb 22 18:10:44 cessna182 kernel: [   83.205315] ata3.00: configured for UDMA/133
Feb 22 18:10:44 cessna182 kernel: [   83.214331] PM: resume of devices complete after 4630.297 msecs
Feb 22 18:10:44 cessna182 kernel: [   83.219563] ALSA sound/usb/mixer.c:846 5:2: cannot get min/max values for control 2 (id 5)
Feb 22 18:10:44 cessna182 acpid: client 1040[0:0] has disconnected
Feb 22 18:10:45 cessna182 kernel: [   83.220033] Restarting tasks ... done.
Feb 22 18:10:45 cessna182 acpid: client connected from 1040[0:0]
Feb 22 18:10:45 cessna182 acpid: 1 client rule loaded
Feb 22 18:10:45 cessna182 rtkit-daemon[1370]: Successfully made thread 2235 of process 1613 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Feb 22 18:10:45 cessna182 NetworkManager[819]: <info> wake requested (sleeping: yes  enabled: yes)
Feb 22 18:10:45 cessna182 NetworkManager[819]: <info> waking up and re-enabling...
Feb 22 18:10:45 cessna182 NetworkManager[819]: <info> WWAN now enabled by management service
Feb 22 18:10:45 cessna182 NetworkManager[819]: <info> (wlan0): now managed
Feb 22 18:10:45 cessna182 NetworkManager[819]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> wake requested (sleeping: yes  enabled: yes)
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> waking up and re-enabling...
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> WWAN now enabled by management service
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): now managed
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 22 18:10:45 cessna182 NetworkManager[819]: <info> (wlan0): bringing up device.
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): bringing up device.
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): preparing device.
Feb 22 18:10:45 cessna182 NetworkManager[819]: <info> (wlan0): preparing device.
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (wlan0): deactivating device (reason 'managed') [2]
Feb 22 18:10:45 cessna182 NetworkManager[819]: <info> (wlan0): deactivating device (reason 'managed') [2]
Feb 22 18:10:45 cessna182 kernel: [   84.236188] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 22 18:10:45 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (eth0): now managed
Feb 22 18:10:46 cessna182 NetworkManager[819]: <info> (eth0): now managed
Feb 22 18:10:46 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 22 18:10:46 cessna182 NetworkManager[819]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 22 18:10:46 cessna182 NetworkManager[819]: NetworkManager[819]: <info> (eth0): bringing up device.
Feb 22 18:10:46 cessna182 NetworkManager[819]: <info> (eth0): bringing up device."

2) "Initial commandline parameters: 
Wed Feb 22 18:10:33 PST 2012: Running hooks for suspend.
Running hook /usr/lib64/pm-utils/sleep.d/00logging suspend suspend:
Linux cessna182.localdomain 3.2.6-3.fc16.x86_64 #1 SMP Mon Feb 13 20:35:42 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Module                  Size  Used by
fuse                   77538  3 
vboxpci                23198  0 
vboxnetadp             13382  0 
vboxnetflt             23424  0 
vboxdrv               263468  3 vboxpci,vboxnetadp,vboxnetflt
ip6t_REJECT            12939  2 
nf_conntrack_ipv6      14290  7 
nf_defrag_ipv6         18139  1 nf_conntrack_ipv6
ip6table_filter        12815  1 
ip6_tables             26976  1 ip6table_filter
nf_conntrack_ipv4      14622  7 
nf_defrag_ipv4         12673  1 nf_conntrack_ipv4
xt_state               12578  14 
nf_conntrack           82331  3 nf_conntrack_ipv6,nf_conntrack_ipv4,xt_state
snd_hda_codec_analog    93565  1 
nvidia              12123658  40 
arc4                   12529  2 
rt61pci                31718  0 
crc_itu_t              12579  1 rt61pci
rt2x00pci              13988  1 rt61pci
rt2x00lib              47983  2 rt61pci,rt2x00pci
uvcvideo               71509  0 
mac80211              439421  2 rt2x00pci,rt2x00lib
snd_hda_intel          33276  1 
cfg80211              194802  2 rt2x00lib,mac80211
snd_hda_codec         114615  2 snd_hda_codec_analog,snd_hda_intel
videodev               97776  1 uvcvideo
nv_tco                 13564  0 
snd_usb_audio         125353  1 
media                  20408  2 uvcvideo,videodev
rfkill                 21410  2 cfg80211
v4l2_compat_ioctl32    16726  1 videodev
snd_hwdep              17611  2 snd_hda_codec,snd_usb_audio
snd_usbmidi_lib        24763  1 snd_usb_audio
joydev                 17412  0 
snd_seq                64807  0 
i2c_nforce2            13166  0 
hid_logitech_dj        18415  0 
forcedeth              63344  0 
ppdev                  17635  0 
snd_pcm                97100  3 snd_hda_intel,snd_hda_codec,snd_usb_audio
snd_rawmidi            29530  1 snd_usbmidi_lib
snd_seq_device         14129  2 snd_seq,snd_rawmidi
amd64_edac_mod         23795  0 
edac_core              51619  3 amd64_edac_mod
snd_timer              28815  2 snd_seq,snd_pcm
snd                    74425  15 snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hwdep,snd_usbmidi_lib,snd_seq,snd_pcm,snd_rawmidi,snd_seq_device,snd_timer
soundcore              14484  1 snd
snd_page_alloc         18101  2 snd_hda_intel,snd_pcm
eeprom_93cx6           13088  1 rt61pci
edac_mce_amd           22882  1 amd64_edac_mod
parport_pc             28082  0 
k8temp                 12971  0 
i2c_core               37955  3 nvidia,videodev,i2c_nforce2
parport                44515  2 ppdev,parport_pc
serio_raw              13371  0 
asus_atk0110           18687  0 
uinput                 17606  0 
ata_generic            12899  0 
pata_acpi              13027  0 
sata_nv                31831  4 
pata_amd               14111  0 
             total       used       free     shared    buffers     cached
Mem:       2052356     885484    1166872          0      48064     431792
-/+ buffers/cache:     405628    1646728
Swap:      4128764          0    4128764

/usr/lib64/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/00powersave suspend suspend:

/usr/lib64/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/01grub suspend suspend:

/usr/lib64/pm-utils/sleep.d/01grub suspend suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/49bluetooth suspend suspend:

/usr/lib64/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/55NetworkManager suspend suspend:
Having NetworkManager put all interfaces to sleep...Done.

/usr/lib64/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/56atd suspend suspend:

/usr/lib64/pm-utils/sleep.d/56atd suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/56dhclient suspend suspend:

/usr/lib64/pm-utils/sleep.d/56dhclient suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/75modules suspend suspend:

/usr/lib64/pm-utils/sleep.d/75modules suspend suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/90clock suspend suspend:

/usr/lib64/pm-utils/sleep.d/90clock suspend suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/94cpufreq suspend suspend:

/usr/lib64/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/95led suspend suspend:

/usr/lib64/pm-utils/sleep.d/95led suspend suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/95packagekit suspend suspend:

/usr/lib64/pm-utils/sleep.d/95packagekit suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
nVidia binary video drive detected, not using quirks.

/usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0

/usr/lib64/pm-utils/sleep.d/99video suspend suspend: success.
Wed Feb 22 18:10:35 PST 2012: performing suspend
Wed Feb 22 18:10:45 PST 2012: Awake.
Wed Feb 22 18:10:45 PST 2012: Running hooks for resume
Running hook /usr/lib64/pm-utils/sleep.d/99video resume suspend:

/usr/lib64/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:

/usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/95packagekit resume suspend:
method return sender=:1.52 -> dest=:1.72 reply_serial=2

/usr/lib64/pm-utils/sleep.d/95packagekit resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/95led resume suspend:

/usr/lib64/pm-utils/sleep.d/95led resume suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/94cpufreq resume suspend:

/usr/lib64/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/90clock resume suspend:

/usr/lib64/pm-utils/sleep.d/90clock resume suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.

/usr/lib64/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/56dhclient resume suspend:

/usr/lib64/pm-utils/sleep.d/56dhclient resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/56atd resume suspend:

/usr/lib64/pm-utils/sleep.d/56atd resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/55NetworkManager resume suspend:
Having NetworkManager wake interfaces back up...Done.

/usr/lib64/pm-utils/sleep.d/55NetworkManager resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/49bluetooth resume suspend:

/usr/lib64/pm-utils/sleep.d/49bluetooth resume suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/01grub resume suspend:

/usr/lib64/pm-utils/sleep.d/01grub resume suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/00powersave resume suspend:

/usr/lib64/pm-utils/sleep.d/00powersave resume suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/00logging resume suspend:

/usr/lib64/pm-utils/sleep.d/00logging resume suspend: success.
Wed Feb 22 18:10:45 PST 2012: Finished."
Comment 2 Ferdinand Badescu 2012-02-23 03:04:01 UTC 
As an added comment: the system (i.e., all the installed software) is up-to-date. By rebooting back to kernel-3.1.9-1, the computer, once again, suspends correctly.
Comment 3 Dave Jones 2012-03-22 16:48:34 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 4 Dave Jones 2012-03-22 16:52:59 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 5 Dave Jones 2012-03-22 17:03:38 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 6 Ferdinand Badescu 2012-03-29 06:09:23 UTC 
Retested with kernel-3.3.0-4.fc16. Suspend still does not work properly. As before, when I issue the suspend command, it goes in suspend mode, then almost immediately wakes up. Now, however, the graphics card remains in suspend mode - the screen is blank - and cannot be brought online. The only way to resume the computer functionality is to press the computer power button for 4 seconds in order to turn off the computer, then restart it after 30 seconds. Even pressing the Reset button would not wake up the video card. Reverting back to kernel-3.1.9-1.fc16 for suspend functionality.

The last know kernel known to have the suspend mode working properly on my computer was kernel-3.2.3. Unfortunately, I don't have it anymore (it's been removed by subsequent kernel upgrades), and I cannot find in the repository.

Below is the computer hardware profile (output from smolt):

General
=================================
UUID: 679549d0-e580-4fe3-90e8-3978e9e0a22d
OS: Fedora release 16 (Verne)
Default run level: Unknown
Language: en_US.utf8
Platform: x86_64
BogoMIPS: 4018.24
CPU Vendor: AuthenticAMD
CPU Model: AMD Athlon(tm) 64 Processor 3200+
CPU Stepping: 0
CPU Family: 15
CPU Model Num: 47
Number of CPUs: 1
CPU Speed: 2000
System Memory: 2003
System Swap: 4031
Vendor: System manufacturer
System: System Product Name System Version
Form factor: Desktop
Kernel: 3.3.0-4.fc16.x86_64
SELinux Enabled: 1
SELinux Policy: targeted
SELinux Enforce: Enforcing
MythTV Remote: Unknown
MythTV Role: Unknown
MythTV Theme: Unknown
MythTV Plugin: 
MythTV Tuner: -1


Devices
=================================
(4318:620:4318:52100) pci, snd_hda_intel, MULTIMEDIA, ASUSTeK Computer Inc. A8N-VM CSM Mainboard
(4318:623:0:0) pci, None, PCI/PCI, MCP51 PCI Bridge
(4318:612:4163:33216) pci, nForce2_smbus, SERIAL, MCP51 SMBus
(4318:609:4163:33216) pci, None, PCI/ISA, MCP51 LPC Bridge
(4318:766:4163:33215) pci, None, RAM, C51 Memory Controller 1
(4318:760:4163:33215) pci, None, RAM, C51 Memory Controller 5
(4318:753:4163:33215) pci, None, RAM, C51 Host Bridge
(4318:762:4163:33215) pci, None, RAM, C51 Memory Controller 0
(4318:639:4163:33215) pci, None, RAM, C51 Memory Controller 3
(4318:638:4163:33215) pci, None, RAM, C51 Memory Controller 2
(4318:761:4163:33215) pci, None, RAM, C51 Memory Controller 4
(4318:767:4163:33215) pci, None, RAM, C51 Host Bridge
(4130:4353:0:0) pci, None, HOST/PCI, K8 [Athlon64/Opteron] Address Map
(4130:4352:0:0) pci, None, HOST/PCI, K8 [Athlon64/Opteron] HyperTransport Technology Configuration
(4130:4355:0:0) pci, k8temp, HOST/PCI, K8 [Athlon64/Opteron] Miscellaneous Control
(4130:4354:0:0) pci, amd64_edac, HOST/PCI, K8 [Athlon64/Opteron] DRAM Controller
(4318:1026:14402:51027) pci, nvidia, VIDEO, G84 [GeForce 8600 GT]
(4318:764:4318:0) pci, pcieport, PCI/PCI, C51 PCI Express Bridge
(4318:617:4163:33130) pci, forcedeth, BRIDGE, MCP51 Ethernet Controller
(4318:765:4318:0) pci, pcieport, PCI/PCI, C51 PCI Express Bridge
(6164:769:5943:85) pci, rt61pci, NETWORK, WMP54G ver 4.1
(4318:613:4163:33216) pci, pata_amd, STORAGE, MCP51 IDE
(4318:624:4163:33216) pci, None, RAM, MCP51 Host Bridge
(4318:614:4163:33216) pci, sata_nv, STORAGE, MCP51 Serial ATA Controller
(4318:763:4318:0) pci, pcieport, PCI/PCI, C51 PCI Express Bridge
(4318:621:4163:33216) pci, ohci_hcd, USB, MCP51 USB Controller
(4318:622:4163:33216) pci, ehci_hcd, USB, MCP51 USB Controller


Filesystem Information
=================================
device mtpt type bsize frsize blocks bfree bavail file ffree favail
-------------------------------------------------------------------
/dev/sda4 / ext4 4096 4096 51137456 39190220 36630220 12804096 11991394 11991394
/dev/sda5 /home ext4 4096 4096 69707276 49132426 45643070 17448960 17306165 17306165
/dev/sda2 /boot ext4 1024 1024 304430 220861 205501 76912 76687 76687

Please let me know if you need additional information.

Ferdinand Badescu.
Comment 7 Ferdinand Badescu 2012-03-30 16:33:51 UTC 
Fri Mar 30 2012:

Tried again  for kernel-3.3.0-4.fc16, this time in multi-user.target (init 3).
With 'pm-suspend', the machine does the following:
- blinking cursor for about 30 seconds; then,
- the computer tries to go in suspend mode, the HDD shuts down; then,
- system awakes within 1 second; then,
- screen is completely black; AND,
- cannot switch between terminals (tty2, 3, etc.); then,
- pressing the Power button shuts down the system. In a normal suspend mode, pressing the Power button would wake up the computer.

Apparently, the BIOS information has not been recorded by smolt. Here it is:
AMIBIOS, ASUS A8N-VM ACPI BIOS Revision 0702

Will re-test later using quirks, and add the testing results to comments.
Comment 8 Ferdinand Badescu 2012-05-26 05:33:08 UTC 
Created attachment 586972 [details]
Output of the command ' lsmod >lsmod.txt'

The file lists all the modules loaded on the system at the time I was attempting to suspend the computer.
Comment 9 Ferdinand Badescu 2012-05-26 05:51:28 UTC 
Today, Fri May 25, three months since the bug has originally been reported, the bug is still not fixed. I checked to see if the bug has been fixed with every kernel release. Tested this evening with the latest kernel:

[ferdi@cessna182 ~]$ uname -r
3.3.7-1.fc16.x86_64

What the computer does when trying to put it in suspend mode:
- the screen goes blank
- a prompt blinks in the upper left corner of the screen
- HDD continues to spin
- all fans - CPU, video card, case - continue to spin
- any key presses or commands issued at the keyboard have no visible effect
- pressing the "Power" switch on the case has no effect
- pressing "Reset" button with hard reset the computer
- pressing "Power" button after a hard reset puts the computer in power off mode

Please let me know if you need additional information, and if so, what information you need to fix this bug. Alternatively, let me know if you stopped trying to fix this bug. As it stands now it has become very annoying to have to shut down the computer every time me or one of the other users finish working on it.
Comment 10 James Preston 2012-06-07 05:17:04 UTC 
I too want to report the same problems and Ferdinand Badescu. 

 uname -r
3.3.7-1.fc16.x86_64

Symptoms are almost the same but ... vary slightly between a blinking cursor with no response to any keyboard input to some parts of a system startup screen (not BIOS but Linux boot) and no keyboard response. The only way to get the system to work is a hard power off and restart.

If you need any further information, please let me know what and specific commands to retreive the info would be helpful. Have been using Redhat Linux since version 6 but .... ya neva know everything :^)
Comment 11 Josh Boyer 2012-09-04 17:13:06 UTC 
Any luck with the 3.4 or 3.5 kernel updates?
Comment 12 Ferdinand Badescu 2012-09-10 05:14:41 UTC 
No luck. Still using kernel-3.1.0-7.fc16 in order to have suspend function working. (Thank goodness I still have F16 installation DVD.) Latest tested kernel: kernel-3.5.3-1.fc17.x86_64.
Comment 13 Josh Boyer 2012-09-10 12:58:58 UTC 
(In reply to comment #12)
> No luck. Still using kernel-3.1.0-7.fc16 in order to have suspend function
> working. (Thank goodness I still have F16 installation DVD.) 

If you are booted into 3.1 when you do a yum update, yum won't remove the 3.1 kernel.  You shouldn't need to manually reinstall it from a DVD.
Comment 14 Ferdinand Badescu 2012-09-21 19:45:06 UTC 
Right! However, I didn't have it installed, having been removed by previous updates.

Anyway, I still believe the problem is related to the NVidia chipset driver in the kernel: I just finished building a new computer, this time using an Intel solution (Core i5, chipset Z77), and the system suspends as it should. It's annoying I had to spend a large amount of money to upgrade hardware that was working so well otherwise. But, since the engineers weren't able (or didn't want) to fix this problem for such a long time, I've been pushed to make the upgrade. Oh, well! It is what it is.