[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <076665b9-9fb1-71da-5f7d-4d2c7f892103@quicinc.com>
Date: Tue, 15 Jun 2021 10:50:31 -0400
From: Qian Cai <quic_qiancai@...cinc.com>
To: Mark Rutland <mark.rutland@....com>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Miles Chen <miles.chen@...iatek.com>,
Andrew Morton <akpm@...ux-foundation.org>
CC: Linux-Next Mailing List <linux-next@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
Will Deacon <will@...nel.org>, <lkft-triage@...ts.linaro.org>,
<regressions@...ts.linux.dev>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ardb@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Christophe Leroy <christophe.leroy@...roup.eu>
Subject: Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c
On 6/15/2021 9:19 AM, Mark Rutland wrote:
> Looking some more, it looks like that's correct in isolation, but it
> clashes with commit:
>
> 5831eedad2ac6f38 ("mm: replace CONFIG_NEED_MULTIPLE_NODES with CONFIG_NUMA")
Just a data point. Reverting the commit alone fixed the same crash for me.
Powered by blists - more mailing lists