From nobody Thu Jan 18 01:51:37 2024
X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TFm1y5J10z57KYX
	for <freebsd-arm@mlmmj.nyi.freebsd.org>; Thu, 18 Jan 2024 01:51:34 +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 4TFm1y2NWDz4fbr
	for <freebsd-arm@freebsd.org>; Thu, 18 Jan 2024 01:51:34 +0000 (UTC)
	(envelope-from fbsd@www.zefox.net)
Authentication-Results: mx1.freebsd.org;
	none
Received: from www.zefox.net (localhost [127.0.0.1])
	by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 40I1pbeb041110
	(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO);
	Wed, 17 Jan 2024 17:51:38 -0800 (PST)
	(envelope-from fbsd@www.zefox.net)
Received: (from fbsd@localhost)
	by www.zefox.net (8.17.1/8.15.2/Submit) id 40I1pb1S041109;
	Wed, 17 Jan 2024 17:51:37 -0800 (PST)
	(envelope-from fbsd)
Date: Wed, 17 Jan 2024 17:51:37 -0800
From: bob prohaska <fbsd@www.zefox.net>
To: Mark Millard <marklmi@yahoo.com>
Cc: freebsd-arm@freebsd.org
Subject: Re: sshd signal 11 on -current
Message-ID: <ZaiEKUf+HJC+LA4F@www.zefox.net>
References: <Zaf5sdzTOGWvW5CR@www.zefox.net>
 <7EF12F55-70E4-4780-BF73-3C7B963C3781@yahoo.com>
 <Zagwxf5U8Ns9qxxp@www.zefox.net>
 <F1538D0F-162A-4F9A-A201-675BCDE5AC19@yahoo.com>
 <ZahvY+1k508rPDTl@www.zefox.net>
 <A3F7BCC1-04EF-482E-8DE2-37327AA7435F@yahoo.com>
List-Id: Porting FreeBSD to ARM processors <freebsd-arm.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-arm
List-Help: <mailto:freebsd-arm+help@freebsd.org>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Subscribe: <mailto:freebsd-arm+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-arm+unsubscribe@freebsd.org>
Sender: owner-freebsd-arm@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A3F7BCC1-04EF-482E-8DE2-37327AA7435F@yahoo.com>
X-Rspamd-Queue-Id: 4TFm1y2NWDz4fbr
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]

On Wed, Jan 17, 2024 at 05:09:32PM -0800, Mark Millard wrote:
> 
> So far it sounds like the problem requires pi4 RasPiOS
> workstation behavior to be involved to get the problem.
> Can you do something to avoid all use of RasPiOS, possibly
> using a different OS on that RPi4B for some experiments?
> 
I just tried a Windows 10 laptop wired into the LAN. Ssh to 
ns2.zefox.net and  running 
grep -i /var/log/messages produces five lines of grep matches, 
then "corrupted MAC on input....." 

I'm not sure which MAC (as in ethernet MAC) is being referred
to. Might a different kind of MAC exist, unrelated to ethernet? 

Running top, or cat /var/log/messages, produces the error
immediately. It seems safe to use ls. Meanwhile, the serial 
console session served by nemesis.zefox.com  is still up 
and usable. 

I'm increasingly confused about where the error starts.

Thanks for reading!

bob prohaska