Date: Tue, 12 Feb 2013 16:32:23 +0100 From: "Ronald Klop" <ronald-freebsd8@klop.yi.org> To: freebsd-arm@freebsd.org Subject: Re: sshd dying on BeagleBone Message-ID: <op.wsef39e08527sy@212-182-167-131.ip.telfort.nl> In-Reply-To: <20130211191608.06a3b3e5@ivory.local> References: <20130211191608.06a3b3e5@ivory.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Feb 2013 01:16:08 +0100, Brett Wynkoop <wynkoop@wynn.com> wrote: > Greeting- > > While looking at the console I saw that sshd died on signal 11! So now > we have a clue. If I recall correctly signal 11 is a seg fault. > > -Brett > You recall correctly. But a seg fault can have multiple reasons like a programming error in ssh or corrupted memory (like errors in the kernel which shuffle pages or whatever) or faulty memory chips so a pointer is flipped or .... Do you have a core dump from ssh? If not you should configure the machine to make them. You can instruct where core files are dumped. My ARM computer says: $ sysctl kern | grep core kern.corefile: %N.core kern.nodump_coredump: 0 kern.coredump: 1 kern.sugid_coredump: 0 But my amd64 desktop has this: kern.corefile: /var/tmp/%U.%N.core See 'man core' for more information. Regards, Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wsef39e08527sy>