Created attachment 709274 [details] part of the var log messages from attempt to suspendd to back to the gnome Description of problem: Cannot suspend on kernels 3.8.1 and 3.8.2, I had no problems on 3.7.9 Version-Release number of selected component (if applicable): How reproducible: Nearly every time. Steps to Reproduce: 1. Select suspend from gnome or press off button or close the notebook lid. Actual results: 1. With the pressing the suspend in gnome nothing happens, except those two informations in var/log/messages: Mar 13 11:11:33 lwpcomp kernel: [ 59.934911] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead. Mar 13 11:11:40 lwpcomp upowerd[1726]: (upowerd:1726): UPower-Linux-WARNING **: no voltage values, using 10V as approximation 2. When pressing the power off button on notebook, the screen goes into console, waits blinking or sometimes display messages probably from var/log/messages, then comes back to gnome. Expected results: Proper suspend, blinking suspend led on notebook. Additional info:
The same happens here on my desktop system running Fedora 18 and kernel 3.8.4-202.fc18.x86_64. When I suspend the system, everything seems to shut down properly (harddisk and fans spin down), but a console cursor keeps flashing on the screen. The power LED does not blink, as it did when the system was suspended. After a few seconds, the system wakes up again by itself. There seems to be nothing strange in the /var/log/pm-suspend.log, however there are these suspicious lines on dmesg: [ 8003.028932] sd 4:0:0:0: [sda] Stopping disk [ 8033.704035] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 8033.704037] ata5.00: failed command: STANDBY IMMEDIATE [ 8033.704042] ata5.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8033.704043] ata5.00: status: { DRDY } [ 8033.704046] ata5: hard resetting link [ 8033.704047] ata5: nv: skipping hardreset on occupied port [ 8034.158032] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8034.167265] ata5.00: configured for UDMA/133 [ 8034.167267] ata5.00: device reported invalid CHS sector 0 [ 8034.167274] ata5: EH complete [ 8034.167287] sd 4:0:0:0: [sda] START_STOP FAILED [ 8034.167289] sd 4:0:0:0: [sda] [ 8034.167290] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 8034.167291] sd 4:0:0:0: [sda] [ 8034.167294] Sense Key : Aborted Command [current] [descriptor] [ 8034.167294] sd 4:0:0:0: [sda] [ 8034.167296] Add. Sense: No additional sense information [ 8034.167305] dpm_run_callback(): scsi_bus_suspend+0x0/0x40 returns 134217730 [ 8034.167309] PM: Device 4:0:0:0 failed to suspend async: error 134217730 [ 8034.167366] PM: Some devices failed to suspend Previous setups were able to suspend the system successfully, so it seems to be a regression in Fedora 18.
The bug remains up to date. I can suspend as many times as I want the first time I boot with new kernel, but when I reboot than I cannot suspend anymore. Could anyone at least have a look and comment? It is really annoying to be stuck on 3.7.9 kernel and with incoming Fedora 19 it will be impossible. I am willing to provide any other logs, etc., just tell me what.
Does this still happen with a 3.9 kernel?
Very rarely, maybe due to a different reason now. I think the bug can be closed.
OK, thank you.