Print this page
12144 Convert Intro(7) to mandoc
12145 Convert cpr(7) to mandoc
12146 Convert ibmf(7) to mandoc
12147 Convert FSS(7) to mandoc
Reviewed by: Peter Tribble <peter.tribble@gmail.com>

Split Close
Expand all
Collapse all
          --- old/usr/src/man/man7/cpr.7.man.txt
          +++ new/usr/src/man/man7/cpr.7.man.txt
   1    1  CPR(7)                   Device and Network Interfaces                  CPR(7)
   2    2  
   3      -
   4      -
   5    3  NAME
   6      -       cpr - Suspend and resume module
        4 +     cpr - Suspend and resume module
   7    5  
   8    6  SYNOPSIS
   9      -       /platform/'uname -m'/kernel/misc/cpr
        7 +     /platform/i86pc/kernel/misc/amd64/cpr
        8 +     /platform/sun4u/kernel/misc/sparcv9/cpr
  10    9  
  11      -
  12   10  DESCRIPTION
  13      -       The cpr module is a loadable module used to suspend and resume the
  14      -       entire system. You may wish to suspend a system to save power or to
  15      -       power off temporarily for transport. The cpr module should not be used
  16      -       in place of a normal shutdown when performing any hardware
  17      -       reconfiguration or replacement.  In order for the resume operation to
  18      -       succeed, it is important that the hardware configuration remain the
  19      -       same. When the system is suspended, the entire system state is
  20      -       preserved in non-volatile storage until a resume operation is
  21      -       conducted.
       11 +     The cpr module is a loadable module used to suspend and resume the entire
       12 +     system.  You may wish to suspend a system to save power or to power off
       13 +     temporarily for transport.  The cpr module should not be used in place of
       14 +     a normal shutdown when performing any hardware reconfiguration or
       15 +     replacement.  In order for the resume operation to succeed, it is
       16 +     important that the hardware configuration remain the same.  When the
       17 +     system is suspended, the entire system state is preserved in non-volatile
       18 +     storage until a resume operation is conducted.
  22   19  
       20 +     pmconfig(1M) and power.conf(4) are used to configure the suspend-resume
       21 +     feature.
  23   22  
  24      -       pmconfig(1M) and power.conf(4) are used to configure the suspend-resume
  25      -       feature.
       23 +     The speed of suspend and resume operations can range from 15 seconds to
       24 +     several minutes, depending on the system speed, memory size, and load.
  26   25  
       26 +     During resume operation, the SIGTHAW signal is sent to all processes to
       27 +     allow them to do any special processing in response to suspend-resume
       28 +     operation.  Normally applications are not required to do any special
       29 +     processing because of suspend-resume, but some specialized processes can
       30 +     use SIGTHAW to restore the state prior to suspend.  For example, X can
       31 +     refresh the screen in response to SIGTHAW.
  27   32  
  28      -       The speed of suspend and resume operations can range from 15 seconds to
  29      -       several minutes, depending on the system speed, memory size, and load.
       33 +     In some cases the cpr module may be unable to perform the suspend
       34 +     operation.  If a system contains additional devices outside the standard
       35 +     shipped configuration, it is possible that device drivers for these
       36 +     additional devices might not support suspend-resume operations.  In this
       37 +     case, the suspend fails and an error message is displayed.  These devices
       38 +     must be removed or their device drivers unloaded for the suspend
       39 +     operation to succeed.  Contact the device manufacturer to obtain a new
       40 +     version of device driver that supports suspend-resume.
  30   41  
       42 +     A suspend may also fail when devices or processes are performing critical
       43 +     or time-sensitive operations (such as realtime operations).  The system
       44 +     will remain in its current running state.  Messages reporting the failure
       45 +     will be displayed on the console and status returned to the caller.  Once
       46 +     the system is successfully suspended the resume operation will succeed,
       47 +     barring external influences such as a hardware reconfiguration.
  31   48  
  32      -       During resume operation, the SIGTHAW signal is sent to all processes to
  33      -       allow them to do any special processing in response to suspend-resume
  34      -       operation. Normally applications are not required to do any special
  35      -       processing because of suspend-resume, but some specialized processes
  36      -       can use SIGTHAW to restore the state prior to suspend. For example, X
  37      -       can refresh the screen in response to SIGTHAW.
       49 +     Some network-based applications may fail across a suspend and resume
       50 +     cycle.  This largely depends on the underlying network protocol and the
       51 +     applications involved.  In general, applications that retry and
       52 +     automatically reestablish connections will continue to operate
       53 +     transparently on a resume operation; those applications that do not will
       54 +     likely fail.
  38   55  
       56 +INTERFACE STABILITY
       57 +     Unstable
  39   58  
  40      -       In some cases the cpr module may be unable to perform the suspend
  41      -       operation. If a system contains additional devices outside the standard
  42      -       shipped configuration, it is possible that device drivers for these
  43      -       additional devices might not support suspend-resume operations. In this
  44      -       case, the suspend fails and an error message is displayed. These
  45      -       devices must be removed or their device drivers unloaded for the
  46      -       suspend operation to succeed. Contact the device manufacturer to obtain
  47      -       a new version of device driver that supports suspend-resume.
  48      -
  49      -
  50      -       A suspend may also fail when devices or processes are performing
  51      -       critical or time-sensitive operations (such as realtime operations).
  52      -       The system will remain in its current running state. Messages reporting
  53      -       the failure will be displayed on the console and status returned to the
  54      -       caller. Once the system is successfully suspended the resume operation
  55      -       will succeed, barring external influences such as a hardware
  56      -       reconfiguration.
  57      -
  58      -
  59      -       Some network-based applications may fail across a suspend and resume
  60      -       cycle.  This largely depends on the underlying network protocol and the
  61      -       applications involved.  In general, applications that retry and
  62      -       automatically reestablish connections will continue to operate
  63      -       transparently on a resume operation; those applications that do not
  64      -       will likely fail.
  65      -
  66      -ATTRIBUTES
  67      -       See attributes(5) for descriptions of the following attributes:
  68      -
  69      -
  70      -
  71      -
  72      -       +---------------------+-----------------+
  73      -       |   ATTRIBUTE TYPE    | ATTRIBUTE VALUE |
  74      -       +---------------------+-----------------+
  75      -       |Interface stability  | Unstable        |
  76      -       +---------------------+-----------------+
  77      -
  78   59  SEE ALSO
  79      -       pmconfig(1M), uadmin(1M), uadmin(2), power.conf(4), attributes(5)
       60 +     pmconfig(1M), uadmin(1M), uadmin(2), power.conf(4), attributes(5)
  80   61  
       62 +     Writing Device Drivers
  81   63  
  82      -       Writing Device Drivers
  83      -
  84   64  NOTES
  85      -       Certain device operations such as tape and floppy disk activities are
  86      -       not resumable due to the nature of removable media.  These activities
  87      -       are detected at suspend time, and must be stopped before the suspend
  88      -       operation will complete successfully.
       65 +     Certain device operations such as tape and floppy disk activities are not
       66 +     resumable due to the nature of removable media.  These activities are
       67 +     detected at suspend time, and must be stopped before the suspend
       68 +     operation will complete successfully.
  89   69  
       70 +     Suspend-resume is currently supported only on a limited set of hardware
       71 +     platforms.
  90   72  
  91      -       Suspend-resume is currently supported only on a limited set of hardware
  92      -       platforms.
  93      -
  94      -
  95      -
  96      -                                 May 13, 2017                           CPR(7)
       73 +illumos                        January 12, 2020                        illumos
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX