-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2020-01-30 at 11:18 +0100, stakanov wrote:
I did create a paste in
Just a comment: I think it is better to obtain this from the /var/log/messages file instead of dmesg output. It has readable timestamps, for starters, and more context.
I am not good enough to understand what the system actually complains. I do not think it is a memory problem, could be related to the OS instead. The swap fills although the memory remains free. If you sudo swapoff -a the swap turns into memory, the system turns responsive.
I'm unsure I understand :-?
sudo dmesg reveals a flood of entries (disregard the martians, these are due to a vpn.)
You could have edited them out ;-)
I do not understand if, and if which, hardware is failing. Memory does nor reveal errors. Sometimes I get a complaint about CPU3 should not be sleeping. This is all I know. Thanks in advance if somebody understands (and maybe can a bit explain) the output. Why does the swap not return to memory once memory is abundantly available?
Because what is stored there is not requested by anything, so better stay there out of the way. More RAM is free as a result. - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjK15hwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVQkAAn3LXJ8i+ZYAHlPhfuIDx XyKkTLDAAJ9/Ds4ZdnoVvGygVIYfT4agXdGobg== =tfgH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org