From: "Chris Murphy" <lists@colorremedies.com>
To: "Filipe Manana" <fdmanana@kernel.org>,
"Михаил Гаврилов" <mikhail.v.gavrilov@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"Linux regressions mailing list" <regressions@lists.linux.dev>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
"David Sterba" <dsterba@suse.com>,
"Josef Bacik" <josef@toxicpanda.com>
Subject: Re: 6.10/regression/bisected - after f1d97e769152 I spotted increased execution time of the kswapd0 process and symptoms as if there is not enough memory
Date: Tue, 02 Jul 2024 15:46:30 -0400 [thread overview]
Message-ID: <93b5fac5-6315-4f2e-a2df-37ef4bf56f9e@app.fastmail.com> (raw)
In-Reply-To: <CAL3q7H6vG6PEKjcsXtSuq=yks_g-MczAz_-V96QSZCs9ezRZpg@mail.gmail.com>
On Tue, Jul 2, 2024, at 1:22 PM, Filipe Manana wrote:
> On Tue, Jul 2, 2024 at 3:13 PM Mikhail Gavrilov
> <mikhail.v.gavrilov@gmail.com> wrote:
>> Unfortunately, the patch didn't improve anything.
>> kswapd0 still consumes 100% CPU under load.
>> And my system continues to freeze.
>
> Ok, the concerning part is the freezing and high cpu usage.
We're seeing this in Fedora Rawhide, which is always using the most recent mainline kernel.
User first reported June 25 they were experiencing much longer backup times, normal is ~5 minutes, they're taking 1+ hours now, with frequent freezes of the DE, notices kswapd using 100% CPU and then other processes also start hanging with 100% CPU. Resolution is a power cycle and reverting to 6.9 series.
The workload is described as "restic via ssh to a repo on a backup server".
I can try to get more info to narrow down the last known good and first known bad kernels if that's useful.
--
Chris Murphy
next prev parent reply other threads:[~2024-07-02 19:46 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 20:56 6.10/regression/bisected - after f1d97e769152 I spotted increased execution time of the kswapd0 process and symptoms as if there is not enough memory Mikhail Gavrilov
2024-06-26 10:48 ` Filipe Manana
2024-06-26 14:16 ` Mikhail Gavrilov
2024-07-01 9:30 ` Filipe Manana
2024-07-02 14:13 ` Mikhail Gavrilov
2024-07-02 17:22 ` Filipe Manana
2024-07-02 19:46 ` Chris Murphy [this message]
2024-07-03 10:32 ` Filipe Manana
2024-07-03 10:31 ` Filipe Manana
2024-07-03 10:44 ` Filipe Manana
2024-07-03 21:07 ` Andrea Gelmini
2024-07-04 9:48 ` Filipe Manana
2024-07-04 9:56 ` Filipe Manana
2024-07-04 10:50 ` Mikhail Gavrilov
2024-07-04 13:33 ` Andrea Gelmini
2024-07-04 13:47 ` Andrea Gelmini
2024-07-04 14:48 ` Andrea Gelmini
2024-07-04 17:25 ` Filipe Manana
2024-07-04 17:31 ` Filipe Manana
2024-07-04 22:15 ` Andrea Gelmini
2024-07-04 22:23 ` Andrea Gelmini
2024-07-05 11:00 ` Filipe Manana
2024-07-05 6:30 ` Andrea Gelmini
2024-07-05 11:06 ` Filipe Manana
2024-07-05 18:36 ` Mikhail Gavrilov
2024-07-05 23:09 ` Filipe Manana
2024-07-06 0:11 ` Andrea Gelmini
2024-07-06 12:07 ` Andrea Gelmini
2024-07-06 17:37 ` Filipe Manana
2024-07-07 9:41 ` Filipe Manana
2024-07-07 10:15 ` Andrea Gelmini
2024-07-07 10:28 ` Filipe Manana
2024-07-07 11:15 ` Andrea Gelmini
2024-07-07 12:10 ` Filipe Manana
2024-07-07 11:35 ` Mikhail Gavrilov
2024-07-07 12:15 ` Filipe Manana
2024-07-07 19:16 ` Mikhail Gavrilov
2024-07-08 14:15 ` Filipe Manana
2024-07-10 9:24 ` Mikhail Gavrilov
2024-07-10 10:53 ` Filipe Manana
2024-08-11 8:08 ` Jannik Glückert
2024-08-11 15:33 ` Filipe Manana
2024-08-14 21:24 ` Jannik Glückert
2024-08-15 22:21 ` intelfx
2024-08-15 23:17 ` intelfx
2024-08-16 0:02 ` David Sterba
2024-08-16 6:42 ` Andrea Gelmini
2024-08-16 6:47 ` Ivan Shapovalov
2024-08-16 7:45 ` Qu Wenruo
2024-08-16 10:58 ` Filipe Manana
2024-08-16 11:16 ` Ivan Shapovalov
2024-09-26 13:45 ` Filipe Manana
2024-07-04 11:18 ` Andrea Gelmini
2024-07-04 16:38 ` Filipe Manana
2024-07-04 22:32 ` Qu Wenruo
2024-07-05 6:18 ` Andrea Gelmini
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=93b5fac5-6315-4f2e-a2df-37ef4bf56f9e@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
/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