This is a tracking bug for Change: Enable systemd-oomd by default for all variants For more details, see: https://fedoraproject.org/wiki/Changes/EnableSystemdOomd Provide a better experience for Fedora users in out-of-memory (OOM) situations by enabling systemd-oomd by default. Actions taken by systemd-oomd operate on a per-cgroup level, aligning well with the life cycle of systemd units. systemd-oomd primarily uses Linux pressure stall information (PSI) to make decisions based on wasted productivity due to resource shortages; in addition to that, it also supports swap based actions.
Update: I put up https://src.fedoraproject.org/rpms/systemd/pull-request/47 last week which includes all the new patches I upstreamed for the systemd-oomd proposal, and a specfile change to create a new subpackage systemd-oomd-defaults which has the configuration values from the proposal.
Today we reached the Completion deadline (testable) milestone in the Fedora schedule. All approved changes should be in a testable state. If you change is testable, please indicate this by setting the status to MODIFIED. If you need to defer the change to Fedora 35 or withdraw the change entirely, please indicate this in a comment and NEEDINFO bcotton. The 100% code complete deadline is Tuesday 23 February. By that date, your change should be fully implemented and the tracking bug set to ON_QA. For other Fedora 34 milestones, see https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
Created attachment 1756053 [details] systemd-oomd Rawhide VM initial test The change is now testable with: dnf copr enable anitazha/systemd-oomd dnf install systemd-oomd-defaults systemctl start systemd-oomd The attachment shows sample commands and output.
Reminder: The change complete (100% complete) deadline for Fedora 34 changes is Tuesday 23 February. At that point, changes should be 100% code complete, along with supporting documentation where appropriate. Please indicate this by setting the tracker bug for your change to ON_QA.
systemd 247.3-2 is built for F34 and Rawhide and works. https://pagure.io/fedora-comps/pull-request/611 will ensure systemd-oomd-defaults is preinstalled and drop earlyoom.
pls disable for aarch64 pinephone: Feb 21 11:36:04 fedorapine systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer... ░░ Subject: A start job for unit systemd-oomd.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit systemd-oomd.service has begun execution. ░░ ░░ The job identifier is 108. Feb 21 11:36:05 fedorapine systemd-oomd[332]: Pressure Stall Information (PSI) is not supported Feb 21 11:36:05 fedorapine systemd[1]: systemd-oomd.service: Main process exited, code=exited, status=1/FAILURE it's not possible to start this on a pinephone atm.
https://github.com/systemd/systemd/pull/18751 was merged in systemd 248~rc2 which should skip systemd-oomd on pinephone.
Can someone check KDE Spin: https://bugzilla.redhat.com/show_bug.cgi?id=1943954
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.