From owner-freebsd-arm@freebsd.org  Wed Nov 22 21:26:27 2017
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C41E7DF63B0
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Wed, 22 Nov 2017 21:26:27 +0000 (UTC)
 (envelope-from freebsd-arm@sentry.org)
Received: from shadow.sentry.org (shadow.sentry.org [103.78.157.218])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "shadow.sentry.org",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 5BD906AF70
 for <freebsd-arm@freebsd.org>; Wed, 22 Nov 2017 21:26:26 +0000 (UTC)
 (envelope-from freebsd-arm@sentry.org)
Received: from shadow.sentry.org (localhost [127.0.0.1])
 by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id vAMLFxvX014888
 for <freebsd-arm@freebsd.org>; Thu, 23 Nov 2017 08:16:00 +1100 (AEDT)
 (envelope-from freebsd-arm@sentry.org)
Subject: Re: ssh sessions close spontaneously on rpi2
References: <20171118165638.GA47956@www.zefox.net>
 <20171120165832.GA55836@www.zefox.net>
 <FB9B37A4-CD5B-45F7-85A5-9AF1E6174F86@dsl-only.net>
 <20171122173613.GA63035@www.zefox.net>
Cc: freebsd-arm <freebsd-arm@freebsd.org>
From: Trev <freebsd-arm@sentry.org>
Message-ID: <5756fea2-750a-6827-fcc4-163e6f21d264@sentry.org>
Date: Thu, 23 Nov 2017 08:15:59 +1100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Firefox/52.0 SeaMonkey/2.49.1
MIME-Version: 1.0
In-Reply-To: <20171122173613.GA63035@www.zefox.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2
 (shadow.sentry.org [0.0.0.0]); Thu, 23 Nov 2017 08:16:00 +1100 (AEDT)
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2017 21:26:27 -0000

bob prohaska wrote on 23/11/2017 04:36:

[chomp]
> Far as I can tell the problems with ssh disconnection are tied to
> running make -jN processes in /usr/ports.  Make -j4 buildworld in /usr/src
> does not obviously interfere with subsequent ssh connections.
> 
> Running make -j4 -DBATCH in /usr/ports/www/firefox also breaks ssh connections,
> but not quite so fast, it takes a few minutes for new ssh sessions to fail.
> Incidentally, the -DBATCH flag is ignored.
> 
> That make stopped on a stale readline installation. After manually upgrading
> readline, the make was restarted without -j4 in /usr/ports/www/firefox and,
> some ten minutes later, the ssh connections are still working.
> 
> Looks like the trouble is related to make -jN, but only in /usr/ports. It's
> understood the -j option is not a sure thing in ports, but having it
> interfere with ssh connections seems most strange.

I've had similar issues (wireless USB dongle failing and settings being 
corrupted) with FreeBSD 11 Stable - I tracked it down to power usage 
when using make -j (I have two 32GB USB memory dongles also plugged in, 
one of which contains /usr). May be related?