SUMMARY: Error in /var/adm/messages: WARNING: mod_load: cannot lo ad module 'cpr' from krtld. Serious?

Hi,

Thanks to Kelly Ormsby and Ed Rolison for their suggestions which were: 

----------
Hi,

I would try grepping all the readme files in /var/sadm/patch for "cpr" 
(grep cpr /var/sadm/patch/*/README*). I don't know about this problem 
specifically but had a similar error with a Solaris 9 patch that I 
installed (although mine stopped my server from booting :().

I am not sure if this problem would be serious or not but I figure that 
error messages are there for a reason so probably should be got rid of.

Once you find the patch I would double check what its actually for and see 
if you actually need it or not and then uninstall it.

Hope that helps,
Kelly.
----------

and

----------

CPR is what drives power saving in solaris. The fact that it isn't loading
on a server is a good thing :)
To avoid the messages, I'd suggest renaming /etc/rc2.d/S85power - this will
stop the power management starting
alltogether. Also I'd suggest (assuming you have X) running
/usr/dt/bin/dtpower and just making sure there's nothing too
nasty in those settings.
----------

I started with Kelly's advice first and this turned up patches:
109896-19, 109888-24, 108974-31, 108258-23 and 108652-66. The only one with
interesting notes (my determination of 'interesting') on cpr is 108258-23,
however these notes relate mainly to the sun4m architecture while I'm on
sun4u. I then went on to Ed's advice which was basically to stop S85power
from starting up - cpr is power management which you don't want on your
server!. 

Thus I am now satisfied there are no issues cropping up in my messages :-)

Thanks again to Kelly & Ed.

Cheers,

James

 

-----Original Message-----
From: eSolutions, Techlist [mailto:eSolutionsT@misys.com]
Sent: 04 August 2003 17:48
To: 'sunmanagers@sunmanagers.org'
Subject: Error in /var/adm/messages: WARNING: mod_load: cannot load
module 'cpr' from krtld. Serious?


Hi,

I've just finished building Solaris 8 (7/01) (Full install + OEM Support) on
an E250 with the latest recommended patch cluster. Having rebooted the
machine, I noticed the following in /var/adm/messages:

Aug  4 17:17:01 esolutions-a krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/misc/sparcv9/cpr: undefined symbol
'prom_resume_outfuncs'
Aug  4 17:17:01 esolutions-a krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/misc/sparcv9/cpr: undefined symbol
'cpr_platform_enable'
Aug  4 17:17:01 esolutions-a krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/misc/sparcv9/cpr: undefined symbol
'pm_reattach_noinvol_fini'
Aug  4 17:17:01 esolutions-a krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/misc/sparcv9/cpr: undefined symbol
'pm_save_direct_levels'
Aug  4 17:17:01 esolutions-a krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/misc/sparcv9/cpr: undefined symbol
'pm_reattach_noinvol'
Aug  4 17:17:01 esolutions-a krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/misc/sparcv9/cpr: undefined symbol
'prom_suspend_outfuncs'
Aug  4 17:17:01 esolutions-a krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/misc/sparcv9/cpr: undefined symbol
'pm_restore_direct_levels'
Aug  4 17:17:01 esolutions-a krtld: [ID 995402 kern.notice]
/platform/sun4u/kernel/misc/sparcv9/cpr: undefined symbol 'pm_powering_down'
Aug  4 17:17:01 esolutions-a krtld: [ID 472681 kern.notice] WARNING:
mod_load: cannot load module 'cpr'

I've checked the archives and the [similar] question has been asked before
but wasn't summarised. Google also pointed me to that question. Over at
http://www.its.siemens.de/free-eks/solaris/Solaris8-new/911520-14.txt ,
there is a reference to a similar problem which occurs after the
installation of 108528-14, this patch cluster installs 108528-23. There I'm
told that the messages are displayed but aren't anything to worry about -
however I'm going with the adage 'just because you read it on the internet
....'. 

I could wait and see what happens but I have a lot of application testing to
do in a short time frame and don't want environmental issues interfering.
So, I would appreciate it if anyone can shed some light on the errors and
how serious, or not, they are.

Cheers,

James
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers