ultrasparc3@hotmail.com wrote in message

news:<20031024.0153.9043@cable.prodigy.com>...
> In <309e7c98.0311232033.75e7de6e@posting.google.com >
> deja_bhoot2000@yahoo.com (Bhoot Nath) writes:
>
> >the sys-suspend command no longer works.
> >it generates an error dialog box with the message "Suspend is not
> >supported", even when CONSOLE-OWNER is executing the command. The problem
> >has persisted even after a couple complete reboots.
>
> do you have a non-standard boot-file (or diag-file) nvram setting?
> have you run pkgchk to see if any system files are corrupted or missing?
> read the pkgchk manual page for details on the options to use.
> does modinfo state whether or not the cpr kernel module is loaded?
> what does "uadmin 3 2" do when run by root?
> how about "uadmin 3 0"?
> check the end of /var/adm/messages for failure messages.

Thank you for replying to my message, ultrasparc3@hotmail.com. Below are

answers to your questions. My problem is still unresolved, so I would

appreciate further insights from you.

1. ALL of the nvram settings are the same as default, except for

#power-cycles. In particular,

diag-file=blank
diag-device=net
boot-file= blank
boot-device= disk net

2. pkgchk does not report any corrupted files. pkgchk SUNWcpr returns

nothing. pkgchk -l SUNWcpr returns normal things (current status: installed

for all components). pkgchk -l -p /platform/sun4u/kernel/misc/cpr returns

everything normal about that executable.

3. modinfo does not return any lines with cpr info. modinfo|grep cpr returns

nothing.

4. No messages in /var/adm/messages (or messages.*) files about any

suspend/power failures. It has entries that say "Nov 24 xx:yy:zz login_name

cpr: [ID XXX kern.notice] cpr: System is being suspended."

5. uadmin 3 2 does not seem to do anything. The # prompt comes back in the

normal fashion. (As root).

6. uadmin 3 2 does the same thing (as root). The # prompt came back without

doing anything.

7. launching sys-suspend and selecting shutdown works (as does shutdown

called directly). But selecting suspend does the following:

non-root (but console owner): Suspend is nor supported message.
root: Suspend starts, "Saving System State. Please Wait..." message comes,

but the dancingicon on the right never starts, and the process never

completes.

8. It seems the state file (/.CPR file) is being created but the process is

getting stuck somehow. After pressing stop-a, and rebooting, logging in

again, I saw that /.CPR file was about 15 MB in size. I even deleted this

file, and tried the whole process again. Same behavior is exhibited.

/.cpr_default is updated.

9. strings /.CPR returns nothing. strings /.cpr_default returns
DfLt
disk net
true

---------------------
Seems like there are two problems:

(a) non-root but console owner is geiing the "Suspend is not supported"

message, even though the /etc/default/power file has following entries.
PMCHANGEPERM=console-owner
CPRCHANGEPERM=console-owner

(b) as root, suspend starts but never finishes.

Bhoot Nath