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%2BHJC%2BLA4F@www.zefox.net> In-Reply-To: <A3F7BCC1-04EF-482E-8DE2-37327AA7435F@yahoo.com> References: <Zaf5sdzTOGWvW5CR@www.zefox.net> <7EF12F55-70E4-4780-BF73-3C7B963C3781@yahoo.com> <Zagwxf5U8Ns9qxxp@www.zefox.net> <F1538D0F-162A-4F9A-A201-675BCDE5AC19@yahoo.com> <ZahvY%2B1k508rPDTl@www.zefox.net> <A3F7BCC1-04EF-482E-8DE2-37327AA7435F@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZaiEKUf%2BHJC%2BLA4F>