From owner-freebsd-ports@freebsd.org Sat Apr 17 15:47:06 2021 Return-Path: Delivered-To: freebsd-ports@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 DB4735DA855; Sat, 17 Apr 2021 15:47:06 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FMyBK6MPRz4pPB; Sat, 17 Apr 2021 15:47:04 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 13HFl3bP075277 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 17 Apr 2021 08:47:04 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 13HFl34R075276; Sat, 17 Apr 2021 08:47:03 -0700 (PDT) (envelope-from fbsd) Date: Sat, 17 Apr 2021 08:47:03 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Cc: freebsd-ports@freebsd.org, bob prohaska Subject: Re: ssh_dispatch_run_fatal on Rpi4 building www/firefox Message-ID: <20210417154703.GA75118@www.zefox.net> References: <20210414154943.GA48835@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4FMyBK6MPRz4pPB X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [2.90 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RBL_SENDERSCORE_FAIL(0.00)[50.1.20.27:server fail]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; AUTH_NA(1.00)[]; DMARC_NA(0.00)[zefox.net]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm,freebsd-ports]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Apr 2021 15:47:06 -0000 On Sat, Apr 17, 2021 at 02:22:42PM +0100, tech-lists wrote: > Hi, > > On Wed, Apr 14, 2021 at 08:49:43AM -0700, bob prohaska wrote: > > While attempting to compile www/firefox on an RPi4 running -current > > the make process stopped with > > > > Bad packet length 3554809687. > > ssh_dispatch_run_fatal: Connection to 192.168.1.11 port 22: Connection > > Is your compiling done on the microsd? > No, mechanical SATA drive in a USB3 case. The immediate oddity was that make, running in the background, was stopping when the ssh connection dropped. Normally, disconnecting the controlling terminal on a background job doesn't kill the job. > If it is, then that's your problem. The microsd is too slow. It causes > bottlenecks and timeouts all over the place. > Agreed, but this wasn't a timeout. Maybe another misleading error message? After several restarts of make in www/firefox which all stopped with the same error I tried using the serial console. Make ran without complaint and made considerable progress. When I learned of the -E option to ssh I stopped the make session, set up error logging, ran make clean in www/firefox and started over. Make subsequently ran to completion and produced a runnable www/firefox. This tempts me to think whatevever triggered the error was among the dependencies, which is difficult to understand and much harder to repeat. Thanks for replying! bob prohaska