From owner-freebsd-arm@freebsd.org Tue Aug 27 00:03:26 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D110DC0AD5 for ; Tue, 27 Aug 2019 00:03:26 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46HTbx5fSsz44Ft for ; Tue, 27 Aug 2019 00:03:25 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x7R03LPE078339; Mon, 26 Aug 2019 17:03:21 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x7R03LjQ078338; Mon, 26 Aug 2019 17:03:21 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201908270003.x7R03LjQ078338@gndrsh.dnsmgr.net> Subject: Re: RPI2 drops _some_ ssh connection In-Reply-To: <20190826174802.GB34339@www.zefox.net> To: bob prohaska Date: Mon, 26 Aug 2019 17:03:21 -0700 (PDT) CC: freebsd-arm@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46HTbx5fSsz44Ft X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [0.84 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.41)[-0.414,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.44)[0.444,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.14)[-0.137,0]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.15), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.05), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Aug 2019 00:03:26 -0000 > On Mon, Aug 26, 2019 at 10:07:24AM -0700, Rodney W. Grimes wrote: > > > > Are there any OOM errors in the /var/log/messages or other indications > > that the system decided to kill a process or a process exited abnormally? > > Nothing on the console. As an aside, this is a Pi2 with 2G of swap. > So far there haven't been memory or swap issues (yet). > > The cu session is talking to an FTDI usb-serial adapter. If cu gets > crossed up, could it kill the ssh session that started it? Unlikely, unless your directly invoking cu from ssh as in: ssh hostname cu someport In that case if the cu exits for any reason the ssh session shuts down too. If you are doing that you might try ssh'ing in, and then invoking cu from the command prompt, that would put you back at a command prompt, possibly with a reason cu exited, if that is what is going on. > Thanks for posting! > bob prohaska -- Rod Grimes rgrimes@freebsd.org