Re: sshd signal 11 on -current

On Wed, Jan 17, 2024 at 08:22:50PM -0800, Mark Millard wrote:
> On Jan 17, 2024, at 17:51, bob prohaska <fbsd@www.zefox.net> wrote:
> 
> > 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.
> > 
> 
> Note: I'm using unique switch naming below, something
> your diagram does not provide.
> 
> Both the macOS system and the pi4 RasPiOS workstation
> used the path (or so I assume):
> 
> MACHINE<->wifi<->lan<->router<->switchA<->ns2.zefox.net
> 
> What about the Windows 10 laptop test? Same path?
>
 
I've edited http://www.zefox.net/~fbsd/netmap to reflect
the actual placement of hosts relative to the switches.


> Could a MACHINE with the problem be moved to be
> on switchA for EtherNet to see if it still has the
> problem when there (just for the test)? Testing the
> macOS system on switchA to be sure it still works
> could also be of interest.

If by MACHINE you mean the ssh client, pelorus.zefox.org 
is already there, along with ns1, ns2 and www.zefox.net.

It's somewhat curious that going from RPi4 workstation
vi ssh to www.zefox.net and then ssh to ns2 does not
report corrupted MAC, but both machines run armv7
FreeBSD 12.4.4

A three hop connection (RPiOS > www.zefox.net > ns2.zefox.net)
somehow inhibits the corrupted MAC error.  Evidently
there's something special going on among the hosts.

> Could you boot a FreeBSD microsd card in the pi4
> instead and try it as a FreeBSD system to see if
> it still has the problem (while in its usual
> place)? I'm still looking for the same hardware
> context but running a distinct but known OS
> context to see if the problem persists.
> 

Realistically I should probably just set up a microSD using
14-Release and configure it as ns2.zefox.net. That needs doing
anyway and should be done for www.zefox.net and ns1.zefox.net
as a matter of maintenance.  

The dilemma is then armv7 vs aarch64. Armv7 has served well,
and used to fit in 1 GB RAM. Now it's getting tighter. 
Aarch64 is _very_ tight in 1 GB RAM now and will doubtless
get worse. Is there a concensus on which to choose? I gather 
armv7's days are numbered but not up yet.

Thanks for reading!

bob prohaska