From: Qian Cai <cai@lca.pw>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
catalin.marinas@arm.com, Will Deacon <will.deacon@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mhocko@kernel.org, linux-mm@kvack.org, vdavydov.dev@gmail.com,
hannes@cmpxchg.org, cgroups@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] arm64/mm: fix a bogus GFP flag in pgd_alloc()
Date: Wed, 12 Jun 2019 14:35:57 -0400 [thread overview]
Message-ID: <1560364557.5154.2.camel@lca.pw> (raw)
In-Reply-To: <20190612065728.GB4761@rapoport-lnx>
On Wed, 2019-06-12 at 09:57 +0300, Mike Rapoport wrote:
> Hi,
>
> On Tue, Jun 11, 2019 at 08:46:45AM -0400, Qian Cai wrote:
> >
> > > On Jun 11, 2019, at 8:41 AM, Mike Rapoport <rppt@linux.ibm.com> wrote:
> > >
> > > Sorry for the delay, I'm mostly offline these days.
> > >
> > > I wanted to understand first what is the reason for the failure. I've
> > > tried
> > > to reproduce it with qemu, but I failed to find a bootable configuration
> > > that will have PGD_SIZE != PAGE_SIZE :(
> > >
> > > Qian Cai, can you share what is your environment and the kernel config?
> >
> > https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
> >
> > # lscpu
> > Architecture: aarch64
> > Byte Order: Little Endian
> > CPU(s): 256
> > On-line CPU(s) list: 0-255
> > Thread(s) per core: 4
> > Core(s) per socket: 32
> > Socket(s): 2
> > NUMA node(s): 2
> > Vendor ID: Cavium
> > Model: 1
> > Model name: ThunderX2 99xx
> > Stepping: 0x1
> > BogoMIPS: 400.00
> > L1d cache: 32K
> > L1i cache: 32K
> > L2 cache: 256K
> > L3 cache: 32768K
> > NUMA node0 CPU(s): 0-127
> > NUMA node1 CPU(s): 128-255
> > Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics
> > cpuid asimdrdm
> >
> > # dmidecode
> > Handle 0x0001, DMI type 1, 27 bytes
> > System Information
> > Manufacturer: HPE
> > Product Name: Apollo 70
> > Version: X1
> > Wake-up Type: Power Switch
> > Family: CN99XX
> >
>
> Can you please also send the entire log when the failure happens?
https://cailca.github.io/files/dmesg.txt
> Another question, is the problem exist with PGD_SIZE == PAGE_SIZE?
No.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-12 18:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 14:00 [PATCH -next] arm64/mm: fix a bogus GFP flag in pgd_alloc() Qian Cai
2019-06-04 14:23 ` Mark Rutland
2019-06-04 14:30 ` Mark Rutland
2019-06-05 21:33 ` Mike Rapoport
2019-06-04 14:54 ` Mike Rapoport
2019-06-10 11:43 ` Will Deacon
2019-06-10 17:26 ` Qian Cai
2019-06-11 10:03 ` Mark Rutland
2019-06-11 12:41 ` Mike Rapoport
2019-06-11 12:46 ` Qian Cai
2019-06-12 6:57 ` Mike Rapoport
2019-06-12 18:35 ` Qian Cai [this message]
2019-06-11 13:02 ` Mark Rutland
2019-06-13 12:11 ` Mike Rapoport
2019-06-13 13:22 ` Qian Cai
2019-06-13 19:44 ` Mike Rapoport
2019-06-17 15:12 ` Mike Rapoport
2019-06-17 16:36 ` Will Deacon
2019-06-18 6:12 ` Mike Rapoport
2019-06-18 6:54 ` Will Deacon
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=1560364557.5154.2.camel@lca.pw \
--to=cai@lca.pw \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=vdavydov.dev@gmail.com \
--cc=will.deacon@arm.com \
/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).