From owner-freebsd-arm@FreeBSD.ORG  Fri Nov  1 17:45:07 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 5A82E2C5;
 Fri,  1 Nov 2013 17:45:07 +0000 (UTC)
 (envelope-from jiashiun@gmail.com)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com
 [IPv6:2a00:1450:400c:c05::233])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C82DB2CE7;
 Fri,  1 Nov 2013 17:45:06 +0000 (UTC)
Received: by mail-wi0-f179.google.com with SMTP id hm4so1416513wib.0
 for <multiple recipients>; Fri, 01 Nov 2013 10:45:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :cc:content-type;
 bh=ifpLI94017TD1Fxy/1t5sPjX6oBEAGy8egZqpMnuEGM=;
 b=mWU3YOFCzi/bOPIhFXZATCMMuBMi0afoAoeybr0Jsy2rCzakssSPjlsDxe2ElqZFmj
 eolBTe41ylZsiNOsTr7QQJJ5sM+7yYbmERt5887hTG6kNg+RHyYF/2uWJuov8wBFxXDU
 HIb1mAVqwIUa2HBe3JSftjYBu0KW9THHt05gVw7RuIGeNYxHnnelMEPXsgppivCc76JT
 4szMB3HygDMmk1MMSjiIXkcMZ+tWlggXLRy4+vNxfP1H4m+YryOV5MOxNqFLCIHgg09s
 EbuU4+q94v2bm4ULPT8kkqoyFqtfcLBOYgZhnTLe0s1NG4ump/R9d2RK21m66GYaL4cB
 KOSQ==
X-Received: by 10.194.3.78 with SMTP id a14mr273904wja.77.1383327905182; Fri,
 01 Nov 2013 10:45:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.206.132 with HTTP; Fri, 1 Nov 2013 10:44:35 -0700 (PDT)
In-Reply-To: <1383313834.31172.65.camel@revolution.hippie.lan>
References: <CAAvnz_rj43Ww6=mMfnp2u5TA2pWb20vWOqyAtuK08wgzy0dH6A@mail.gmail.com>
 <1383313834.31172.65.camel@revolution.hippie.lan>
From: Jia-Shiun Li <jiashiun@gmail.com>
Date: Sat, 2 Nov 2013 01:44:35 +0800
Message-ID: <CAHNYxxMMF_GJv10drYuQFO+av+Tdp8OBvJfFZObEZ=tgaBovSA@mail.gmail.com>
Subject: Re: sshd crash
To: Ian Lepore <ian@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>,
 Howard Su <howard0su@gmail.com>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Nov 2013 17:45:07 -0000

On Fri, Nov 1, 2013 at 9:50 PM, Ian Lepore <ian@freebsd.org> wrote:
>
> Several people investigated this (pretty extensively) and didn't come up
> with a solution, or even a good suspect.  We haven't forgotten it by any
> means, but I don't think anyone is knocking themselves out on it right
> now either.
>
> A fresh look may be exactly what's needed, so feel free to dig into it.
>
> I'll summarize what I remember...  It happens on armv4 and armv6.  It
> happens when kernel and world are built with clang or gcc.  It happens
> with eabi and oabi.
>
> What I can't remember is whether anyone has bisected things down to a
> changeset or timeframe when the problem showed up.
>

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.