string

Action
On some system architectures, specifically sun4c, the problem could be that different
capacity memory chips are mixed together. Someone might have placed 1MB SIMMs
in the same bank with 4MB SIMMs. If this is so, rearrange the memory chips. Make
sure to put higher-capacity SIMMs in the first bank(s), and lower-capacity SIMMs in
the remaining bank(s); never mix different capacity SIMMs in the same bank.
The problem could also be that cache memory on the motherboard has gone bad and
needs replacement. If main memory is installed correctly, try swapping the
motherboard.
Technical Notes
The best way to isolate the problem is to look at the %pc register to see where it got
its arguments, and why the arguments were bad. If you can reproduce the condition
causing this message, your system vendor might be able to help diagnose the
problem.
"X"
X connection to string:0.0 broken
(explicit kill or server shutdown).
Cause
This means that the client has lost its connection to the X server. The "0.0" represents
the display device, which is usually the console. This message can appear when a
user is running an X application on a remote system with the DISPLAY set back to
the original system and the remote system’s X server disappears, perhaps because
someone exited X windows or rebooted the machine. It sometimes appears locally
when a user exits the window system. Data loss is possible if applications were
killed before saving files.
Action
Try to run the application again in a few minutes after the system has rebooted and
the window system is running.
206 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998