From owner-freebsd-arm@FreeBSD.ORG Sat Nov 2 05:35:39 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DF759FC2; Sat, 2 Nov 2013 05:35:39 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9D50B21F0; Sat, 2 Nov 2013 05:35:39 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id rA25ZU8E077698; Sat, 2 Nov 2013 05:35:30 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.123] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id h95qeta9ijin9mcmzxfw38a2se; Sat, 02 Nov 2013 05:35:30 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: sshd crash From: Tim Kientzle In-Reply-To: <1383343354.31172.102.camel@revolution.hippie.lan> Date: Fri, 1 Nov 2013 22:35:29 -0700 Content-Transfer-Encoding: 7bit Message-Id: References: <1383313834.31172.65.camel@revolution.hippie.lan> <1383328423.31172.92.camel@revolution.hippie.lan> <1383343354.31172.102.camel@revolution.hippie.lan> To: Ian Lepore , Diane Bruce X-Mailer: Apple Mail (2.1510) Cc: freebsd-arm@freebsd.org, Howard Su 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: Sat, 02 Nov 2013 05:35:39 -0000 On Nov 1, 2013, at 3:02 PM, Ian Lepore wrote: > On Sat, 2013-11-02 at 02:40 +0800, Jia-Shiun Li wrote: >> On Sat, Nov 2, 2013 at 1:53 AM, Ian Lepore wrote: >>> On Sat, 2013-11-02 at 01:44 +0800, Jia-Shiun Li wrote: >>>> may I add: putty causes this to happen. mine 0.62. But ssh from another >>>> FreeBSD host has no problem. >>>> >>>> I suspect it to be some issues related to memory or malloc issues >>>> specific to bbb. 'tmux a -d' without existing detached sessions >>>> causes tmux client to core dump. But sshd and it are both fine on rpi. >>>> >>>> -Jia-Shiun. >>> >>> This is the first I've heard of being able to ssh to an arm platform >>> that doesn't have PrivSep disabled, since about July or so. I've never >>> heard a report yet that anything on the client side could make a >>> difference. >>> >>> It's definitely not a beaglebone thing, it happens on every arm board >>> I've got... dreamplug, rpi, bbw, imx53, wandboard. >> >> >> Ok let me make sure I did not mix things up. ;) >> >> IIRC I once saw similar issue on rpi shortly. But after another >> weekly update it was gone. I did not pay too much attention on rpi, >> and thought it was bbb specific. >> >> I did not change sshd_config, UsePrivilegeSeparation supposed >> remaining on as default is. I started looking into it a couple of months ago but didn't get very far; Diane Bruce got a lot further than I did. If I recall correctly, it started up when the malloc libc symbols were changed. That may have altered what malloc implementation sshd used. So it could be a long-standing stray write that jemalloc just happens to detect. It could also be related to locking (there's some multi-threaded crypto code in sshd that may be involved). Tim