Just happened for the second time in 46 hours (and it never happened
before):
kernel: [167836.884337] INFO: task kcompactd0:63 blocked for more than 120
seconds.
kernel: [167836.887341] Not tainted 4.15.0-128-generic #131-Ubuntu
kernel: [167836.889880] "echo 0 > /proc/sys/kernel/hung_task_t
Thank you very much for the quick reply and pointing to the PR.
We are launching hundreds of similar processes on this server ; we
migrated to Noble especially for this new feature (MemoryKSM).
Any idea when the backport will occur? We're eager to try it out.
--
You received this bug notificati
Public bug reported:
In one of my working unit (service), I try to toggle the MemoryKSM
boolean setting.
Using any of:
MemoryKSM=yes
MemoryKSM=on
MemoryKSM=true
MemoryKSM=1
Results in:
Sep 19 16:16:56 systemd[1]: Started XXX.service - XXX service.
Sep 19 16:16:56 (e_server)[4487]: XXX.service:
I have also verified the fix using systemd 255.4-1ubuntu8.5 from noble-
proposed.
I was able to launch the transient unit with MemoryKSM=yes (this step
used to fail without the fix) and now systemctl reports:
# systemctl show povalles-j | grep -i memoryksm
MemoryKSM=yes
Thank you! Now I can mo
