From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 3A8781382C5 for ; Wed, 24 Jun 2020 17:26:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CC6E2E0975; Wed, 24 Jun 2020 17:26:28 +0000 (UTC) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8C4ECE0886 for ; Wed, 24 Jun 2020 17:26:28 +0000 (UTC) Received: by mail-io1-xd2d.google.com with SMTP id y5so3001428iob.12 for ; Wed, 24 Jun 2020 10:26:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Myv3ICZ0j783bFF78VrxpvqrlDjRyALVjD2DjTYkPh4=; b=Ik83YXWII/LlrezBhLULjaPO6S8IgSlu+40vYW97eM552GL0PfdZYgI/IPq+IXmIN3 Zg/mDTDPxL2u3U5cMZ9OSmJJL3G8mynDVm4VEgR2EO9PdxzVVWrXDRqafPbNa/hcNf35 5jE7vE7+3456mxHWgHcSvYQzfhttZWRY2V3hfccsgI90OLtqv2/8Ma3ByHOU6kkpEF1v Q2WorbKAL8FxCp90HosX8F6May8aGP8V00mtQjkctJsJtnO1GKfo76vOHd2Vt6gS/RJK 4J1hbdNUERBaBofb/QSzsAtBLinKFUZ1xvD/ASo699ZGuHaZpSDiAfz/NuHG8s8CEYjC S5mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Myv3ICZ0j783bFF78VrxpvqrlDjRyALVjD2DjTYkPh4=; b=ZdbBWXlvy64npth5l10WdffnL6bM0ZkJJQW42/yTkXzYtuaIsa1CAD4YEJpI3YeT69 lO6SATueteF3ff9NQ1t6qXKQEKS5KnbglcfcGXQe6SWR8vSLP6vKjhiTBD+rtqg1XUFB e8UPUIJR0jCJC3621H9S5dBDYb4gd/Jo0wbAsGuyBVcV6YJaQebGAoOo5kxX32LMPZp2 DM9IL+R2mICkv6RdGcxlfxIDjavw6z0XlFdN5ncs2VPp8+gF+/setRWsHELr/q7Khpvz 9pLFuM7AV5bKrC2XH/orjhgmocEYgVax9WqHTvIqID0PGGdnHkKdC41sSdgI3x7ATiN9 Idsg== X-Gm-Message-State: AOAM533eVEmrA5NYDj74k9wo4RTbla7zmtsbCYrhNrOEvHBdferdUy6W gP29acPs8hwbGEE5NFGnUN+dTu2JUL01a/fhpmTvX8xP1a0= X-Google-Smtp-Source: ABdhPJwUH87n/L4gHFQaMpIeTy9GJbRywQquACb8OCPVjrYJSziuCPQEx63PEBdpwE84GNWB+kzmWStgCLlzKT3xjH8= X-Received: by 2002:a05:6638:1409:: with SMTP id k9mr31456371jad.125.1593019587007; Wed, 24 Jun 2020 10:26:27 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <5614023.31tnzDBltd@lenovo.localdomain> In-Reply-To: <5614023.31tnzDBltd@lenovo.localdomain> From: =?UTF-8?B?0KHQtdGA0LXQs9CwINCk0LjQu9Cw0YLQvtCy?= Date: Wed, 24 Jun 2020 21:26:15 +0400 Message-ID: Subject: Re: [gentoo-user] Suspend-to-ram freezing tasks failed To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="0000000000009a967105a8d7c642" X-Archives-Salt: b334f600-36f4-4afc-a2bd-b6c8a40d6c59 X-Archives-Hash: 81d90922311459934f76f04693f395fc --0000000000009a967105a8d7c642 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. On Wed, Jun 24, 2020, 21:03 Michael wrote: > On Wednesday, 24 June 2020 16:30:25 BST =D0=A1=D0=B5=D1=80=D0=B5=D0=B3=D0= =B0 =D0=A4=D0=B8=D0=BB=D0=B0=D1=82=D0=BE=D0=B2 wrote: > You have OOM messages there. It seems your baloo process eats up all you= r > RAM > and when the time comes to put the OS to sleep, there is not enough RAM t= o > do > so. I don't know if using a swap file or swap partition would help, but > controlling how much baloo is indexing will help both in terms of load on > the > CPU as well as in terms of RAM when awake and RAM when you suspend it. --0000000000009a967105a8d7c642 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hmm, isn't the "OOM killer enabled" jus= t a notification that OOM killer is working (not taking action)?
=
I'm running htop now. It seems that baloo really takes t= oo much RAM and CPU, but nothing fatal, plenty of free physical RAM and swa= p.

Anyway, thanks for the ti= p about baloo, but I think that it'll solve a small part of the problem= .

On Wed, Jun 24, 2020, 21:03 Michael <confabulate@kintzios.com> wrote= :
On Wednesday, = 24 June 2020 16:30:25 BST =D0=A1=D0=B5=D1=80=D0=B5=D0=B3=D0=B0 =D0=A4=D0=B8= =D0=BB=D0=B0=D1=82=D0=BE=D0=B2 wrote:
You have OOM messages there.=C2=A0 It seems your baloo process eats up all = your RAM
and when the time comes to put the OS to sleep, there is not enough RAM to = do
so.=C2=A0 I don't know if using a swap file or swap partition would hel= p, but
controlling how much baloo is indexing will help both in terms of load on t= he
CPU as well as in terms of RAM when awake and RAM when you suspend it.
--0000000000009a967105a8d7c642--