From: Andrew Morton <akpm@linux-foundation.org>
To: howaboutsynergy@pm.me
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [Bug 204165] New: 100% CPU usage in compact_zone_order
Date: Mon, 15 Jul 2019 14:25:24 -0700 [thread overview]
Message-ID: <20190715142524.e0df173a9d7f81a384abf28f@linux-foundation.org> (raw)
In-Reply-To: <bug-204165-27@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sat, 13 Jul 2019 19:20:21 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=204165
>
> Bug ID: 204165
> Summary: 100% CPU usage in compact_zone_order
Looks like we have a lockup in compact_zone()
> Product: Memory Management
> Version: 2.5
> Kernel Version: 5.2.0-g0ecfebd2b524
> Hardware: x86-64
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Page Allocator
> Assignee: akpm@linux-foundation.org
> Reporter: howaboutsynergy@pm.me
> Regression: No
I assume this should be "yes". Did previous kernels exhibit this
behavior or is it new in 5.2?
next parent reply other threads:[~2019-07-15 21:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204165-27@https.bugzilla.kernel.org/>
2019-07-15 21:25 ` Andrew Morton [this message]
2019-07-15 23:28 ` howaboutsynergy
2019-07-16 1:52 ` howaboutsynergy
2019-07-16 3:25 ` howaboutsynergy
2019-07-16 3:57 ` howaboutsynergy
2019-07-16 7:11 ` Mel Gorman
2019-07-16 19:15 ` howaboutsynergy
2019-07-17 17:53 ` Mel Gorman
2019-07-17 22:00 ` howaboutsynergy
2019-07-18 8:37 ` Mel Gorman
2019-07-16 10:03 ` Mel Gorman
2019-07-16 1:08 ` howaboutsynergy
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=20190715142524.e0df173a9d7f81a384abf28f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=howaboutsynergy@pm.me \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
/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