From: howaboutsynergy@protonmail.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [Bug 204165] New: 100% CPU usage in compact_zone_order
Date: Tue, 16 Jul 2019 01:08:25 +0000 [thread overview]
Message-ID: <GpYhzvuVkDasrIKYTwAS5RLC5ooyxn4xFepgkPDSQx7bPotn0HzNue5n9YgatrtqoydkCs8bLshc-ulda3MoaDOoUFM57FTDatWTZ7uRXk0=@protonmail.com> (raw)
In-Reply-To: <20190715142524.e0df173a9d7f81a384abf28f@linux-foundation.org>
[-- Attachment #1.1: Type: text/plain, Size: 1786 bytes --]
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, July 15, 2019 11:25 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> (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?
Is the reason that you switched to email somehow related to bugzilla not even posting this very reply of yours(seen above) that you sent via email even though you included bugzilla in the CC ?! I noticed that only mine got posted and mine was after yours in the emails. Yet there's no trace of yours when looking at the issue through the bugzilla interface.
Your (emailed)comment should be right after this https://bugzilla.kernel.org/show_bug.cgi?id=204165#c11
but it's not.
Anyway, I'm ready to test stuff, please let me know how I can help.
Meanwhile I'll try to find a better way to replicate the issue.
[-- Attachment #1.2: publickey - howaboutsynergy@protonmail.com - 0x947B9B34.asc --]
[-- Type: application/pgp-keys, Size: 3227 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 855 bytes --]
prev parent reply other threads:[~2019-07-16 1:08 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
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 [this message]
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='GpYhzvuVkDasrIKYTwAS5RLC5ooyxn4xFepgkPDSQx7bPotn0HzNue5n9YgatrtqoydkCs8bLshc-ulda3MoaDOoUFM57FTDatWTZ7uRXk0=@protonmail.com' \
--to=howaboutsynergy@protonmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--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