Might be MTU? Can you try what happens with `find /` ?

If it freezes then, too:

On both machines:

ping -s 1252 -D $remote_IP

if it works, increase by half the way to 1472, try if it still works:

ping -s 1362 -D $remote_IP

etc.

If it does not work, you half the distance to the previously working
one, e.g.:

ping -s 1362 -D $remote_IP << works

ping -s 1417 -D $remote_IP << does not work

then next:

ping -s 1390 -D $remote_IP

If you use IPv6, you need to decrease the starting/end value by 20 and
use ping6, i.e., as min 1232 and as max 1452; If the hosts cannot reach
each other directly (NAT), it depends on the path which addr to use;
Would need traceroutes between the hosts then.

The assumption would be that you do have an MTU issue on-path there,
which is not correctly signaled. This only hits as soon as the packets
get a size larger than the MTU, e.g., when typing dmesg (or find /).

With best regards,
Tobias

On Sat, 2024-03-09 at 16:07 +0000, Laura Smith wrote:
> Hi
> 
> I've got a fresh install of 7.4 on a new box and am seeing a very
> weird problem.
> 
> If I enter "dmesg" I get a few lines of output and then it hangs and
> my ssh connection gets dropped.  I ran syspatch, rebooted and the
> problem persists.  
> 
> Example:
> 
> # dmesg
> MX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-
> CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2
> ,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,R
> DTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SM
> EP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,
> WAITPKG,PKS,MD_CLEAR,IBT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_A
> LL,SKIP_L1DFL,MDS_NO,IF_PSCHANGE,TAA_NO,MISC_PKG_CT,ENERGY_FILT,DOITM
> ,SBDR_SSDP_N,FBSDP_NO,PSDP_NO,RRSBA,OVERCLOCK,XSAVEOPT,XSAVEC,XGETBV1
> ,XSAVES
> cpu19: 32KB 64b/line 8-way D-cache, 64KB 64b/line 8-way I-cache, 2MB
> 64b/line 16-way L2 cache, 30MB 64b/line 12-way L3 cache
> cpu19: smt 0, core 35, package 0
> cpu20 at mainbus0: apid 72 (application processor)
> cpu20: 12th Gen Intel(R) Core(TM) i9-12900TE, 3392.18 MHz, 06-97-02,
> patch 00000025
> Timeout, server 10.1.2.3 not responding.

Reply via email to