From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 209733] Starting new KVM virtual machines on PPC64 starts to hang after box is up for a while
Date: Thu, 26 Nov 2020 23:16:48 +0000 [thread overview]
Message-ID: <bug-209733-206035-a2WG4H4ZS5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209733-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209733
Michael Ellerman (michael@ellerman.id.au) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michael@ellerman.id.au
--- Comment #5 from Michael Ellerman (michael@ellerman.id.au) ---
Thanks for persisting with the testing.
I wonder if it was fixed by:
c4629e4e7e09 ("mm/compaction: stop isolation if too many pages are isolated and
we have pages to migrate")
or
38935861d85a ("mm/compaction: count pages and stop correctly during page
isolation")
They fix a potential infinte loop in a path that's used by the HTAB allocation.
Those landed in v5.9.9, and fix a commit that was introduced in v5.7 (which
doesn't match your observation that v5.7.x was OK).
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-11-26 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 23:09 [Bug 209733] New: Starting new KVM virtual machines on PPC64 starts to hang after box is up for a while bugzilla-daemon
2020-10-18 23:13 ` [Bug 209733] " bugzilla-daemon
2020-10-30 17:46 ` bugzilla-daemon
2020-11-07 16:36 ` bugzilla-daemon
2020-11-08 16:33 ` bugzilla-daemon
2020-11-26 17:26 ` bugzilla-daemon
2020-11-26 17:26 ` bugzilla-daemon
2020-11-26 23:16 ` bugzilla-daemon [this message]
2020-11-27 2:26 ` bugzilla-daemon
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=bug-209733-206035-a2WG4H4ZS5@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.