From: Mel Gorman <mgorman@techsingularity.net>
To: Dexuan Cui <decui@microsoft.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Roman Gushchin <guro@fb.com>, Hugh Dickins <hughd@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
"dchinner@redhat.com" <dchinner@redhat.com>,
Greg Thelen <gthelen@google.com>,
Kuo-Hsin Yang <vovoy@chromium.org>
Subject: Re: isolate_lru_pages(): kernel BUG at mm/vmscan.c:1689!
Date: Wed, 8 May 2019 11:33:08 +0100 [thread overview]
Message-ID: <20190508103308.GF18914@techsingularity.net> (raw)
In-Reply-To: <PU1P153MB01693FF5EF3419ACA9A8E1FDBF3B0@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM>
On Wed, May 01, 2019 at 11:49:10PM +0000, Dexuan Cui wrote:
> Hi,
> Today I got the below BUG in isolate_lru_pages() when building the kernel.
>
> My current running kernel, which exhibits the BUG, is based on the mainline kernel's commit
> 262d6a9a63a3 ("Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip").
>
> Looks nobody else reported the issue recently.
>
That is missing some fixes that were merged for 5.1, particularly
6b0868c820ff ("mm/compaction.c: correct zone boundary handling when
resetting pageblock skip hints"). Can you try reproducing this under 5.1
at least?
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2019-05-08 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 23:49 isolate_lru_pages(): kernel BUG at mm/vmscan.c:1689! Dexuan Cui
2019-05-02 12:55 ` Michal Hocko
2019-05-02 18:24 ` Dexuan Cui
2019-05-08 10:33 ` Mel Gorman [this message]
2019-05-08 15:44 ` Dexuan Cui
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=20190508103308.GF18914@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dchinner@redhat.com \
--cc=decui@microsoft.com \
--cc=gthelen@google.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=vdavydov.dev@gmail.com \
--cc=vovoy@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).