From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Suspend-to-ram freezing tasks failed
Date: Wed, 24 Jun 2020 18:35:42 +0100 [thread overview]
Message-ID: <2451840.9Mp67QZiUf@lenovo.localdomain> (raw)
In-Reply-To: <CABf1Ly--BUE4NZ62L6jNPMq7VnLnFzaFAOx9Zm59O4SgQVDF9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
On Wednesday, 24 June 2020 18:26:15 BST Серега Филатов wrote:
> Hmm, isn't the "OOM killer enabled" just a notification that OOM killer is
> working (not taking action)?
>
> I'm running htop now. It seems that baloo really takes too much RAM and
> CPU, but nothing fatal, plenty of free physical RAM and swap.
>
> Anyway, thanks for the tip about baloo, but I think that it'll solve a
> small part of the problem.
It should be easy to test. In Plasma desktop go to SystemSettings > Search >
File Search, then untick 'Enable File Search'. Run 'balooctl disable' to make
sure it is stopped, log out/in for good measure and then shut the lid, or
select to Suspend to Ram from the menu while keeping an eye on the logs.
This has solved suspend problems on some of my systems, but not all. There is
still the odd desktop which misbehaves, randomly.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-06-24 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 15:30 [gentoo-user] Suspend-to-ram freezing tasks failed Серега Филатов
2020-06-24 16:39 ` [gentoo-user] Initial console messages garbled Robin Atwood
2020-06-24 16:54 ` Jack
2020-06-25 6:50 ` Robin Atwood
2020-06-24 17:31 ` tedheadster
2020-06-25 6:55 ` Robin Atwood
2020-06-28 14:20 ` Robin Atwood
2020-06-28 16:29 ` Dale
2020-06-28 14:51 ` Rich Freeman
2020-06-28 16:03 ` Sid Spry
2020-06-24 17:02 ` [gentoo-user] Suspend-to-ram freezing tasks failed Michael
2020-06-24 17:26 ` Серега Филатов
2020-06-24 17:35 ` Michael [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2451840.9Mp67QZiUf@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox