The following section describes solutions to problems that may occur with Suspend-Resume.
If pressing the Power key does not suspend your system, refer to the following procedure.
Verify that the key processing daemon is present:
% ps -eaf | grep speckeysd |
If the resulting message does not list /usr/openwin/bin/speckeysd, you will need to start the key processing daemon.
Become superuser and start the key processing daemon (if necessary):
% /usr/openwin/bin/speckeysd |
When the system fails to suspend, an alert appears. The exact message within the pop-up window may vary, depending on the cause of the problem, but the Suspend Failed window will appear similar to the following figure.
When any Suspend Failed window appears, click either of the buttons at the bottom of the window:
Power Off turns off power without preserving the current operating state, as a suspend operation usually does.
Cancel cancels the suspend request, and the hardware continues to be powered on.
The following sections discuss specific "Suspend Failed" messages.
If a device fails to suspend, a Suspend Failed pop-up window is displayed that includes the following message:
Device error during suspend.
Select Cancel.
If you have not already saved your work, do so now. Take the corrective action described below before retrying suspend again.
Check for more information in the console window in the workspace.
An unsupported device or a device performing nonresumable activity may be the cause of this problem. If the device specified by the console message is performing a nonresumable activity, stop the activity and try suspend again.
If your system contains devices in addition to the default configuration, then these devices may not support the Suspend feature. In that case, continue with the next step.
Before you try to suspend again, attempt to unload the device driver by doing these steps:
You might not be able to unload a driver for one of these reasons:
Another driver must be unloaded first, such as audio(7I) and dbri(7D).
The device is actually in use and busy.
In such a case, contact your system administrator.
Try Suspend again.
If Suspend succeeds, the system saves your activities and the system powers off successfully.
If Suspend does not succeed, the alert pop-up window is displayed again. In this case, continue with the next step.
Save your work if you have not already done so.
Select Power Off.
Since the error persists, suspend is not possible. Selecting Power Off shuts down the system properly without causing file system damage. (Remember, your data will not be saved unless you have saved it manually.) When you power on again, your system automatically reboots.
However, if you select Power Off and it fails, your system does not support software power off. An alert pop-up window is then displayed with information about the power-off failure, as shown in the following figure:
Select Continue.
Your system might not support software power off due to a non-Type 5 keyboard or an outdated system PROM. If you do have a Type 5 keyboard installed, then contact your system provider for a system PROM upgrade.
Also, some sun4m-architecture systems drop to an OpenBootTM PROM prompt after a suspend operation, because those systems do not support software power off.
Save your work if you have not already done so.
Halt the operating system.
Power off by pressing the power switch on the back panel of the system to the off (0) position.
When possible, solve the problem for that device in the future by obtaining and installing a device driver that supports Suspend features, if one is available from your manufacturer.
If a process fails to suspend, a Suspend Failed pop-up window is displayed that includes the following message:
Process can not be stopped.
Follow this procedure in response to this message.
Select Cancel.
If you have not already saved your work, do so now. Retry Suspend again.
Check for more information in the Console window in the Workspace.
If a process is a real-time process or if it is performing certain special network operations, that process may refuse to suspend gracefully. In most cases, this is only a temporary condition and you can correct it by trying Suspend again.
However, if the problem persists, stop the offending process (as specified in the console message) and retry Suspend again.
Try Suspend again.
If Suspend succeeds, the system saves your activities and the system powers off.
If Suspend does not succeed, the alert pop-up window is displayed again.
Save your work if you have not already done so.
Select Power Off.
Remember, your data will not be saved unless you have done so manually.
When you power on again, your system automatically reboots.
When your system suspends, it creates a statefile to preserve the current state of your system. If the file system containing the statefile is full, a Suspend Failed pop-up window is displayed that includes the following message:
Suspend requires more disk space for statefile.
Perform the following procedure in response to this message.
Select Cancel.
You'll need to take corrective action before you can try Suspend again.
If you have not already saved your work, do so now.
Check for more information in the Console window in the Workspace.
You must have a minimum of 10 MBytes of space available. Clean up a partition before you try suspend again. Another solution is to change the location of the statefile to a file system with sufficient space, as described in the power.conf(4) man page.
Contact your system administrator for assistance, if necessary.
Try Suspend again.
If Suspend succeeds, the system saves your activities and the system powers off.
If Suspend does not succeed, the alert pop-up window is displayed again. In that case, continue with the next step.
Save your work if you have not already done so.
Select Power Off.
Remember, your data will not be saved unless you have done so manually.
When you power on again, your system automatically reboots.
If an abnormal condition occurs, a Suspend Failed pop-up window is displayed that includes the following message:
Abnormal condition during suspend.
Perform the following procedure in response to this message.
Select Cancel.
You'll need to take corrective action before you can try to suspend again.
If you have not already saved your work, do so now.
Check for more information in the Console window in the Workspace.
You may be able to take further corrective action by checking the console error messages.
Try Suspend again.
If Suspend succeeds, the system saves your activities and the system powers off.
If Suspend does not succeed, the alert pop-up window is displayed again. In this case, continue with the next step.
Save your work if you have not already done so.
Select Power Off.
Remember, your data won't be saved unless you have done so manually.
When you power on again, your system automatically reboots.
After a Resume, the system's screen lock is invoked by default. To disable the screen lock before you use the power key to Suspend, use the following procedure.
You cannot disable screen locking that is put into effect by AutoShutdown. This is a security feature. It ensures that only someone who knows your password can get access to your work session when the system resumes.
Modify the speckeysd.map file to add the -x flag to the sys-suspend entry.
For more information, see the man page for speckeysd.map(4).
Save your work if you have not already done so.
Exit the current windowing session and restart.
In place of this step, you may also kill the speckeysd daemon and then restart the daemon.