string

SYSLOGD CAUSES SYSTEM HANGS
Cause
(Over and Over again = installpatch problems)
syslog service starting.
Cause
During system reboot, this message might appear and the boot seems to hang. After
starting syslogd(1M) service, the system runs /etc/rc2.d/S75cron, which in
turn calls ps(1). Sometimes after an abrupt system crash /dev/bd.off becomes a
link to nowhere, causing the ps(1) command to hang indefinitely.
Action
Reboot single user (for example with boot -s) and run ls -l /dev/bd* to see if
this is the problem. If so, remove /dev/bd.off, then run bdconfig off or reboot
with the -r (reconfigure) option.
This is the most commonly reported situation that causes ps(1) to hang.
System booting after fatal error FATAL
Cause
The system reboots automatically. Afterward, the messages file contains
System booting after fatal error FATAL.
The message is issued during a reboot after the system detects a hardware error.
Things which can cause this are: UPA address parity error, Master queue overflows,
DTAG parity errors, E-Cache tag parity errors, and Coherence errors.
Action
Use prtdiag(1M) to help identify failed hardware components. The errors indicate
either have a bad CPU module or a bad system board.
Alphabetical Message Listing 179