From nobody Thu Jan 18 14:45:51 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 4TG5Ck28r5z58Ryl for ; Thu, 18 Jan 2024 14:46:10 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.123]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4TG5Ck0C1lz4fbZ for ; Thu, 18 Jan 2024 14:46:10 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2601:5cf:407e:55c1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 659582A717; Thu, 18 Jan 2024 09:46:02 -0500 (EST) Content-Type: text/plain; charset=utf-8 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Subject: Re: sshd signal 11 on -current From: Paul Mather In-Reply-To: Date: Thu, 18 Jan 2024 09:45:51 -0500 Cc: Mark Millard , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <47E5939E-0DCF-4666-AB62-4A8E8A3F3204@gromit.dlib.vt.edu> References: <7EF12F55-70E4-4780-BF73-3C7B963C3781@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Rspamd-Queue-Id: 4TG5Ck0C1lz4fbZ 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:1312, ipnet:128.173.0.0/16, country:US] On 17 Jan 2024, at 8:51=E2=80=AFpm, bob prohaska = wrote: > On Wed, Jan 17, 2024 at 05:09:32PM -0800, Mark Millard wrote: >>=20 >> 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? >>=20 > I just tried a Windows 10 laptop wired into the LAN. Ssh to=20 > ns2.zefox.net and running=20 > grep -i /var/log/messages produces five lines of grep matches,=20 > then "corrupted MAC on input....."=20 >=20 > I'm not sure which MAC (as in ethernet MAC) is being referred > to. Might a different kind of MAC exist, unrelated to ethernet? If this error is from SSH then it is likely unrelated to Ethernet. It = likely refers to Message Authentication Code (MAC), which is used to = ensure data integrity. See man ssh_config(5) for details. Cheers, Paul.=