linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Tibor Bana <bana.tibor@gmail.com>
Cc: Mel Gorman <mgorman@techsingularity.net>, Jan Kara <jack@suse.cz>,
	Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	vbabka@suse.cz, aarcange@redhat.com, rientjes@google.com,
	mhocko@kernel.org, zi.yan@cs.rutgers.edu, hannes@cmpxchg.org
Subject: Re: [regression -next0117] What is kcompactd and why is he eating 100% of my cpu?
Date: Tue, 26 Jan 2021 03:52:16 -0500	[thread overview]
Message-ID: <178586.1611651136@turing-police> (raw)
In-Reply-To: <20210125195438.c8d0e7980da0c2931d4f3056@gmail.com>

On Mon, 25 Jan 2021 19:54:38 +0100, Tibor Bana said:

> I don't know if it still actual, but I am strugling with this problem right
> now and searching the internet for solutions. I read the thread and saw that
> you are strugling to reproduce the problem, and I can reproduce it almost every
> day.

I'm pretty sure that you have a real bug on your hands.  Even if your box
is very low on memory, kcompactd should eventually figure out it's not
making any progress and wait for the situation to change before trying again.

However, I'm also pretty sure that it's a different one than the one we were
chasing, because that one never showed up again once all the patches landed in
linux-next, some 18 months before 5.9 was released.


  reply	other threads:[~2021-01-26 18:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 20:00 [regression -next0117] What is kcompactd and why is he eating 100% of my cpu? Pavel Machek
2019-01-27  2:56 ` valdis.kletnieks
2019-01-27 14:09   ` Mel Gorman
2019-01-27 14:15   ` Mel Gorman
2019-01-27 16:00     ` Pavel Machek
2019-01-27 21:36       ` valdis.kletnieks
2019-01-28  9:16         ` Jan Kara
2019-01-28 10:57           ` Sergey Senozhatsky
2019-01-28 11:03           ` Mel Gorman
2019-01-30  1:06           ` valdis.kletnieks
2019-01-30  4:29             ` valdis.kletnieks
2019-01-30 10:40               ` Mel Gorman
2021-01-25 18:54                 ` Tibor Bana
2021-01-26  8:52                   ` Valdis Klētnieks [this message]
2021-01-26  9:17                   ` Mel Gorman
2021-01-27 19:29                     ` Tibor Bana
2021-02-16 12:36                   ` Jason A. Donenfeld
2021-02-16 22:33                     ` Valdis Klētnieks

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=178586.1611651136@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=aarcange@redhat.com \
    --cc=akpm@osdl.org \
    --cc=bana.tibor@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rientjes@google.com \
    --cc=vbabka@suse.cz \
    --cc=zi.yan@cs.rutgers.edu \
    /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;
as well as URLs for NNTP newsgroup(s).