Yes. That triggered a memory of the reason my system (Linux Mint) was doing the same thing. It was caused by ipv6 queries that went nowhere, I do not need ipv6 and Comcast does not support it afaik, so I disabled it and everything is fine now.
On Sun, Nov 3, 2024 at 2:37 PM Paul Heinlein <[email protected]> wrote: > On Sat, 2 Nov 2024, American Citizen wrote: > > > Tomas: > > > > I did a fairly good look into the /var folder. > > > > I don't see anything much from either the dmesg log or journalctl.log > > > > My system is still going into paralysis mode. For example I went to > > edit the logs in the var/log area and vim was halted for several > > seconds > > An unlikely but possible culprit: DNS. Is the first server entry in > your /etc/resolv.conf file valid? If so, does it resolve IPv4 and IPv6 > queries? > > DNS resolution delays impact systems in unexpected ways. > > Like I said: unlikely, but worth checking. > > -- > Paul Heinlein > [email protected] > 45°22'48" N, 122°35'36" W >
