-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
both nohang tests failed on Ubuntu 18.04 #98
Comments
Hi! I'd like to see the output:
See also #85 |
And i'd like to see the journal since nohang starts.
|
|
|
2 reboots in the journal are power cycles after freezes. |
PSI required to prevent freezing under heavy swapping. You could install the new kernel (4.20+), maybe 5.0 or 5.3. |
Also disabling swap space can help you to prevent freezeng: this will help to avoid prolonged swapping. Demo without swapping: https://youtu.be/UCwZS5uNLu0 |
It is ok for me. However, according to README PSI is not required.
What if I have only 8 GB of RAM? I remember I read in some article that it is better to have swap enabled. I only have SSD in this system. Theoretically, swap speed should be fast. Could you please clarify about swap? |
for basic usage, i e to handle low MemAvailable/SwapFree.
As you see, it is not fast enough to prevent freezing.
Yes, later, plz wait. |
Yes, the article is https://chrisdown.name/2018/01/02/in-defence-of-swap.html |
App works as intended. It responds to low MemAvailable and SwapFree. As you see:
My fault is that the documentation is terrible and I did not explain what "basic usage" is.
I think that the problem would be resolved if you waited 30 minutes. The memory will be freed after filling the swap and killing the victim. The situation can be improved by reducing the size of the swap space. Small swap space may be filled faster and corrective action will happen faster. Using PSI metrics allows you to detect freezing faster and perform corrective action less than one minute. |
Thank you for the detailed replies. I plan to post the update here after I have some progress. This may take some time depending on how much time I can dedicate to this issue. |
Actually I thought one of the features of earlyoom, nohang and alike is avoiding waiting such a long time. |
See https://itsfoss.com/ubuntu-hwe-kernel/ Maybe you would run Hardware Enablement Stacks (HWE) are incorporated into installers for select Ubuntu LTS (Long Term Support) point releases. It is a special Ubuntu feature that provides an LTS release with hardware support introduced in newer Ubuntu releases. https://packages.ubuntu.com/en/bionic/linux-generic-hwe-18.04 |
Without swap space you can avoid waiting. nohang without PSI works like earlyoom: it responds to MemAvailable and SwapFree. |
So I have installed Linux kernel 5.3.0 according to provided suggestion. One more question is why after killing the hog process the memory isn't freed?
|
Processes do not free memory immediately after receiving a signal, even if it is SIGKILL. Freeing up memory can take up to several seconds. See also rfjakob/earlyoom#128 (comment) |
Do you still run Ubuntu 18.04? Or did you meanwhile upgrade to 20.04 or 22.04? |
I upgraded to 20.04. |
@lvitya what is holding you from going 22.04? |
The transition introduces a bunch of problems. The conclusion is based on my previous experience. |
I agree something is fishy going on with Ubuntu, here is my solutions. https://github.com/alexmyczko/autoexec.bat/tree/master/config.sys |
I have installed nohang as described. Then
And guess what - system freezed. After waiting for 10 minutes I performed a power cycle.
After booting I checked if nohang is running with
$ systemctl list-units
This time I tried
$ tail /dev/zero
The system freezed again.
Is this me doing something wrong or the app? For me as a user this behaviour is not expected.
The text was updated successfully, but these errors were encountered: