From owner-freebsd-arm@FreeBSD.ORG Tue Feb 12 15:32:32 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BFCF19A0 for ; Tue, 12 Feb 2013 15:32:32 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from cpsmtpb-ews10.kpnxchange.com (cpsmtpb-ews10.kpnxchange.com [213.75.39.15]) by mx1.freebsd.org (Postfix) with ESMTP id 56156B6B for ; Tue, 12 Feb 2013 15:32:32 +0000 (UTC) Received: from cpsps-ews16.kpnxchange.com ([10.94.84.197]) by cpsmtpb-ews10.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Tue, 12 Feb 2013 16:31:06 +0100 Received: from CPSMTPM-TLF104.kpnxchange.com ([195.121.3.7]) by cpsps-ews16.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Tue, 12 Feb 2013 16:31:06 +0100 Received: from sjakie.klop.ws ([212.182.167.131]) by CPSMTPM-TLF104.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Tue, 12 Feb 2013 16:32:24 +0100 Received: from 212-182-167-131.ip.telfort.nl (localhost [127.0.0.1]) by sjakie.klop.ws (Postfix) with ESMTP id 24B6D5C95 for ; Tue, 12 Feb 2013 16:32:24 +0100 (CET) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-arm@freebsd.org Subject: Re: sshd dying on BeagleBone References: <20130211191608.06a3b3e5@ivory.local> Date: Tue, 12 Feb 2013 16:32:23 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20130211191608.06a3b3e5@ivory.local> User-Agent: Opera Mail/12.14 (FreeBSD) X-OriginalArrivalTime: 12 Feb 2013 15:32:24.0404 (UTC) FILETIME=[27FC1940:01CE0936] X-RcptDomain: freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 15:32:32 -0000 On Tue, 12 Feb 2013 01:16:08 +0100, Brett Wynkoop 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.