From: Mel Gorman <mgorman@techsingularity.net>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>, Qian Cai <cai@lca.pw>,
linux-mm@kvack.org, vbabka@suse.cz
Subject: Re: kernel BUG at include/linux/mm.h:1020!
Date: Tue, 26 Mar 2019 12:03:27 +0000 [thread overview]
Message-ID: <20190326120327.GK3189@techsingularity.net> (raw)
In-Reply-To: <CABXGCsNFNHee3Up78m7qH0NjEp_KCiNwQorJU=DGWUC4meGx1w@mail.gmail.com>
On Tue, Mar 26, 2019 at 09:03:07AM +0500, Mikhail Gavrilov wrote:
> > Ok, thanks.
> >
> > Trying one last time before putting together a debugging patch to see
> > exactly what PFNs are triggering as I still have not reproduced this on a
> > local machine. This is another replacement that is based on the assumption
> > that it's the free_pfn at the end of the zone that is triggering the
> > warning and it happens to be the case the end of a zone is aligned. Sorry
> > for the frustration with this and for persisting.
> >
> > diff --git a/mm/compaction.c b/mm/compaction.c
> > index f171a83707ce..b4930bf93c8a 100644
> > --- a/mm/compaction.c
> > +++ b/mm/compaction.c
>
> <SNIP>
>
> I do not want to hurry, but it looks like this patch has fixed the problem.
> I will watch for a day.
> But the system has already experienced a night without a hang (kernel panic).
>
Good news (for now at least). I've written an appropriate changelog and
it's ready to send. I'll wait to hear confirmation on whether your
machine survives for a day or not. Thanks.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2019-03-26 12:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:55 Mikhail Gavrilov
2019-03-15 20:58 ` Daniel Jordan
2019-03-15 21:34 ` Qian Cai
2019-03-17 15:22 ` Mel Gorman
2019-03-19 19:14 ` Qian Cai
2019-03-19 19:27 ` Pavel Tatashin
2019-03-19 19:35 ` Qian Cai
2019-03-19 23:13 ` Pavel Tatashin
2019-03-19 23:26 ` Qian Cai
2019-03-20 14:20 ` Mel Gorman
2019-03-20 21:50 ` Mikhail Gavrilov
2019-03-21 5:39 ` Mikhail Gavrilov
2019-03-21 13:21 ` Qian Cai
2019-03-21 15:08 ` Mikhail Gavrilov
2019-03-21 15:48 ` Qian Cai
2019-03-21 18:57 ` Mikhail Gavrilov
2019-03-21 19:14 ` Qian Cai
2019-03-22 3:41 ` Mikhail Gavrilov
2019-03-22 13:43 ` Qian Cai
2019-03-22 11:15 ` Mel Gorman
2019-03-23 4:40 ` Mikhail Gavrilov
2019-03-25 10:58 ` Mel Gorman
2019-03-25 16:06 ` Mikhail Gavrilov
2019-03-25 20:31 ` Mel Gorman
2019-03-26 4:03 ` Mikhail Gavrilov
2019-03-26 12:03 ` Mel Gorman [this message]
2019-03-27 3:57 ` Mikhail Gavrilov
2019-03-27 8:54 ` Mel Gorman
2019-03-22 7:39 ` Oscar Salvador
2019-03-22 7:54 ` Mikhail Gavrilov
2019-03-22 8:55 ` Oscar Salvador
2019-03-22 8:56 ` Oscar Salvador
2019-03-22 17:49 ` Mikhail Gavrilov
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=20190326120327.GK3189@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=cai@lca.pw \
--cc=daniel.m.jordan@oracle.com \
--cc=linux-mm@kvack.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=vbabka@suse.cz \
/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