On Mon, 30 Dec 2002, Wojciech Puchar wrote:

> Core was generated by `telnetd'.
> Program terminated with signal 11, Segmentation fault.

> #0  0x804ab7d in telnet_spin ()
> #1  0x804f242 in telnet_spin ()
> #2  0x804db29 in telnet_spin ()
> #3  0x804dff5 in telnet_spin ()
> #4  0x804d9f5 in telnet_spin ()
> #5  0x804a04e in encrypt_end ()

You said:
> in logs i found lots (every few seconds) messages like
> telnetd[9872]: ttloop:  peer died: No such file or directory

This could happen from telnet-based monitoring software or possibly
malicious telnet probes that don't properly quit their connection.

Did the timestamp on the core file match the ttloop log entry?

If not, maybe the Signal 11 segmentation fault was related to just some
bad ram, overheated CPU, or loose hardware connections. But it could be
software related.

   Jeremy C. Reed
   http://bsd.reedmedia.net/