picld errors after adding new CPUs
Posted by Ceri Davies Fri, 24 Mar 2006 19:28:00 GMT
I added a new system board to one of our v880s this afternoon, after which picld(1M) spat out the following errors on boot, despite all diagnostics having passed:
Mar 24 16:48:21 vleappc picld[320]: ERROR running psvc_check_temperature_policy_0
on CPU5_DIE_TEMPERATURE_SENSOR (2757672)
Mar 24 16:48:21 vleappc picld[320]: ERROR running psvc_check_temperature_policy_0
on CPU5_DIE_TEMPERATURE_SENSOR (2757672)
Mar 24 16:48:21 vleappc picld[320]: No such file or directory
Mar 24 16:48:21 vleappc picld[320]: No such file or directory
Mar 24 16:48:21 vleappc picld[320]: ERROR running psvc_check_temperature_policy_0
on CPU7_DIE_TEMPERATURE_SENSOR (2757768)
Mar 24 16:48:21 vleappc picld[320]: No such file or directory
Mar 24 16:48:21 vleappc picld[320]: ERROR running psvc_check_temperature_policy_0
on CPU7_DIE_TEMPERATURE_SENSOR (2757768)
Mar 24 16:48:21 vleappc picld[320]: No such file or directory
The solution is as simple as a reconfigure boot.
Update [07/04/2006]: Chris Mackowski mailed me to point out that devfsadm -C works just nice too, of course. Thanks Chris.
