All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: <linux-kernel@vger.kernel.org>
Subject: 5.1 kernel: khugepaged stuck at 100%
Date: Thu, 9 May 2019 05:54:56 -0400	[thread overview]
Message-ID: <002901d5064d$42355ea0$c6a01be0$@lucidpixels.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]

Hello,

Kernel: 5.1 (self-compiled, no modules)
Arch: x86_64
Distro: Debian Testing

Issue: I was performing a dump of ext3 and ext4 filesystems and then
restoring them to a separate volume (testing)-- afterwards I noticed that
khugepaged is stuck at 100% CPU. It is currently still stuck at 100% CPU, is
there anything I can do to debug what is happening prior to a reboot to work
around the issue?  I have never seen this behavior prior to 5.1. 

$ cat /proc/cmdline
auto BOOT_IMAGE=5.1.0-2 ro root=901 3w-sas.use_msi=1 nohugeiomap
page_poison=1 pcie_aspm=off pti=on rootfstype=ext4 slub_debug=P
zram.enabled=1 zram.num_devices=12 zswap.enabled=1 zswap.compressor=lz4
zswap.zpool=z3fold

$ 5.1 .config attached: config.txt.gz

$ attachment: graphic.JPG -> graph of the processes, dark green ->
khugepaged

$ top

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   77 root      39  19       0      0      0 R 100.0   0.0  23:29.27
khugepaged
    1 root      20   0  171800   7832   4948 S   0.0   0.0   1:25.59 systemd
    2 root      20   0       0      0      0 S   0.0   0.0   0:00.02
kthreadd
    3 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 rcu_gp
    4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00
rcu_par_gp
    6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00
kworker/0+
    8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00
mm_percpu+

Thoughts on debugging / before reboot to clear this up?

Thanks,

Justin.

[-- Attachment #2: config.txt.gz --]
[-- Type: application/x-gzip, Size: 23869 bytes --]

[-- Attachment #3: graphic.JPG --]
[-- Type: image/jpeg, Size: 80182 bytes --]

             reply	other threads:[~2019-05-09  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09  9:54 Justin Piszcz [this message]
2019-05-09 11:13 ` 5.1 kernel: khugepaged stuck at 100% Kirill A. Shutemov
2019-05-15  7:25   ` Justin Piszcz
2019-05-16 14:14   ` Justin Piszcz
2019-05-16 14:17     ` Justin Piszcz
2019-05-16 14:27       ` Justin Piszcz
2019-05-24 11:43         ` Oleksandr Natalenko
2019-06-06 17:24     ` Max Kellermann
2019-06-07  7:40       ` Max Kellermann
2019-06-07  7:50         ` Oleksandr Natalenko
2019-06-07  7:53         ` Max Kellermann
2019-05-09 11:17 ` Justin Piszcz

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='002901d5064d$42355ea0$c6a01be0$@lucidpixels.com' \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.