Bug 10526

Summary:	suspend to ram fail
Product:	Mageia	Reporter:	Denis Prost <denis.prost>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	denis.prost
Version:	3
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	pm-utils-1.4.1-6.mga3	CVE:
Status comment:

Description Denis Prost 2013-06-14 07:10:49 CEST

When suspending to ram either from GUI or performing pm-suspend on command line (either as plain user or as root), suspend starts but seems to fail during the process and the system wakes up.
Here is the log :

----------------------
Jun 14 06:54:37 localhost kernel: Suspending console(s) (use no_console_suspend to debug) 
Jun 14 06:54:37 localhost kernel: legacy_suspend(): pnp_bus_suspend+0x0/0x70 returns -5 
Jun 14 06:54:37 localhost kernel: PM: Device 00:09 failed to suspend: error -5 
Jun 14 06:54:38 localhost kernel: PM: Some devices failed to suspend 
Jun 14 06:54:40 localhost systemd[1]: systemd-suspend.service: main process exited, code=exited, status=1/FAILURE 
Jun 14 06:54:40 localhost systemd[1]: Job suspend.target/start failed with result 'dependency'. 
Jun 14 06:54:40 localhost systemd[1]: Unit systemd-suspend.service entered failed state 
Jun 14 06:54:37 localhost kernel: Suspending console(s) (use no_console_suspend to debug) 
Jun 14 06:54:37 localhost kernel: legacy_suspend(): pnp_bus_suspend+0x0/0x70 returns -5 
Jun 14 06:54:37 localhost kernel: PM: Device 00:09 failed to suspend: error -5 
Jun 14 06:54:38 localhost kernel: PM: Some devices failed to suspend 
Jun 14 06:54:40 localhost systemd[1]: systemd-suspend.service: main process exited, code=exited, status=1/FAILURE 
Jun 14 06:54:40 localhost systemd[1]: Job suspend.target/start failed with result 'dependency'. 
Jun 14 06:54:40 localhost systemd[1]: Unit systemd-suspend.service entered failed state 
-----------------------

Reproducible: 

Steps to Reproduce:

Denis Prost 2013-06-14 07:11:01 CEST

CC: (none) => denis.prost

Comment 1 Denis Prost 2013-06-15 20:30:21 CEST

solved ! The problem came from the fact that I was using kernel-server. I switched to kernel-desktop and the problem is gone !

Status: NEW => RESOLVED
Resolution: (none) => FIXED