[TriLUG] scp interrupted system call with copy from Ubuntu 18.04 sys to 20.04 sys

[Pete Soper via TriLUG]

Today on this system  "dl" running 20.04 (with all updates/upgrades) I 
was doing an "scp -r rick:tms ." and got this and the copy is hung:

/tms/vendor/BNO080/STM32 Nucleo-64/nucleo-f411re.pdf: truncate: 
Interrupted system call
nucleo-f411re.pdf                             100%   24MB 3.4MB/s   00:06
./tms/vendor/BNO080/STM32 Nucleo-64/nucleo-f411re.pdf: Interrupted 
system call
BNO080-Development-Kit-for-Nucleo-Quick-Start   0%    0 0.0KB/s   --:-- ETA

It's still in the hung state in case there's something I could do to get 
more information. There is nothing in /var/log/syslog or kern.log. Both 
machines are 64 bit Intel-based.

What forum or place would I poke around to see if this is a known 
problem and whether there's a patch for it and how do I frame my 
search/question (e.g. what is the formal name of the chunk of Linux this 
is likely to involve?).

The network hardware hasn't been changed in years except a few weeks ago 
I put a gigabit switch between three of the machines on wired ethernet 
from the router and rick is one of them (longest cable run about eight 
feet). Maybe I should run scp all night and see if I can flush out more 
failures and then take the gigabit switch out and repeat the experiment, 
or would this be a silly waste of effort?

Thanks,
Pete