[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <AFCC92A8-8D2F-4A52-9656-7627904D0AFE@lca.pw>
Date: Mon, 27 Apr 2020 09:45:31 -0400
From: Qian Cai <cai@....pw>
To: Mike Rapoport <rppt@...ux.ibm.com>
Cc: Mel Gorman <mgorman@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
Michal Hocko <mhocko@...nel.org>,
David Hildenbrand <david@...hat.com>,
Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>, Baoquan He <bhe@...hat.com>
Subject: Re: compaction: VM_BUG_ON_PAGE(!zone_spans_pfn(page_zone(page), pfn))
> On Apr 26, 2020, at 10:41 AM, Mike Rapoport <rppt@...ux.ibm.com> wrote:
>
> Hi,
>
> On Thu, Apr 23, 2020 at 05:25:56PM -0400, Qian Cai wrote:
>> Compaction starts to crash below on linux-next today. The faulty page belongs to Node 0 DMA32 zone.
>> I’ll continue to narrow it down, but just want to give a headup in case someone could beat me to it.
>>
>> Debug output from free_area_init_core()
>> [ 0.000000] KK start page = ffffea0000000040, end page = ffffea0000040000, nid = 0 DMA
>> [ 0.000000] KK start page = ffffea0000040000, end page = ffffea0004000000, nid = 0 DMA32
>> [ 0.000000] KK start page = ffffea0004000000, end page = ffffea0012000000, nid = 0 NORMAL
>> [ 0.000000] KK start page = ffffea0012000000, end page = ffffea0021fc0000, nid = 4 NORMAL
>>
>> I don’t understand how it could end up in such a situation. There are several recent patches look
>> more related than some others.
>
> Can you please add "mminit_loglevel=4 memblock=debug" to the kernel
> command line?
https://cailca.github.io/files/dmesg.txt
Powered by blists - more mailing lists