From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, lkp@lists.01.org, lkp@intel.com,
"Md. Haris Iqbal" <haris.iqbal@ionos.com>,
Jack Wang <jinpu.wang@ionos.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org
Subject: Re: [locking/lockdep] 4051a81774: page_allocation_failure:order:#,mode:#(GFP_KERNEL),nodemask=(null)
Date: Mon, 20 Jun 2022 11:42:07 +0200 [thread overview]
Message-ID: <YrBA7ysAif4I9nPv@linutronix.de> (raw)
In-Reply-To: <20220620020727.GA3669@xsang-OptiPlex-9020>
+ rtrs, infiniband folks.
On 2022-06-20 10:07:27 [+0800], kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: 4051a81774d6d8e28192742c26999d6f29bc0e68 ("locking/lockdep: Use sched_clock() for random numbers")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git locking/urgent
…
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
>
…
> [ 17.451787][ T1] rtrs_server L2256: Loading module rtrs_server, proto 2.0: (max_chunk_size: 131072 (pure IO 126976, headers 4096) , sess_queue_depth: 512, always_invalidate: 1)
> [ 17.470894][ T1] swapper: page allocation failure: order:5, mode:0xcc0(GFP_KERNEL), nodemask=(null)
If I read this right, it allocates "512 * 10" chunks of order 5 / 128KiB
of memory (contiguous memory). And this appears to fail.
This is either a lot of memory or something that shouldn't be used on
i386.
Either way, locking/urgent is innocent.
> [ 17.470905][ T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-rc2-00001-g4051a81774d6 #1
…
> [ 17.471016][ T1] Node 0 active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:350872kB isolated(anon):0kB isolated(file):0kB mapped:0kB dirty:0kB writeback:0kB shmem:0kB writeback_tmp:0kB kernel_stack:304kB pagetables:4kB all_unreclaimable? no
> [ 17.471022][ T1] DMA free:2304kB boost:0kB min:80kB low:100kB high:120kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
> [ 17.471029][ T1] lowmem_reserve[]: 0 544 2867 2867
> [ 17.471034][ T1] Normal free:3040kB boost:0kB min:2940kB low:3672kB high:4404kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:16348kB writepending:0kB present:749560kB managed:671404kB mlocked:0kB bounce:0kB free_pcp:900kB local_pcp:900kB free_cma:0kB
> [ 17.471041][ T1] lowmem_reserve[]: 0 0 18591 18591
> [ 17.471045][ T1] HighMem free:2040716kB boost:0kB min:512kB low:3652kB high:6792kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:334524kB writepending:0kB present:2379656kB managed:2379656kB mlocked:0kB bounce:0kB free_pcp:296kB local_pcp:296kB free_cma:0kB
> [ 17.471052][ T1] lowmem_reserve[]: 0 0 0 0
> [ 17.471056][ T1] DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 1*256kB (U) 0*512kB 0*1024kB 1*2048kB (U) 0*4096kB = 2304kB
> [ 17.471073][ T1] Normal: 4*4kB (UM) 2*8kB (UM) 2*16kB (U) 3*32kB (UM) 3*64kB (UM) 1*128kB (M) 2*256kB (M) 0*512kB 2*1024kB (M) 0*2048kB 0*4096kB = 3040kB
> [ 17.471093][ T1] HighMem: 1*4kB (M) 1*8kB (U) 0*16kB 0*32kB 0*64kB 1*128kB (M) 1*256kB (U) 1*512kB (M) 2*1024kB (UM) 1*2048kB (M) 497*4096kB (M) = 2040716kB
> [ 17.471114][ T1] 87718 total pagecache pages
> [ 17.471116][ T1] 786302 pages RAM
> [ 17.471116][ T1] 594914 pages HighMem/MovableOnly
> [ 17.471117][ T1] 19697 pages reserved
> [ 17.471118][ T1] 0 pages hwpoisoned
Sebastian
next prev parent reply other threads:[~2022-06-20 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 2:07 kernel test robot
2022-06-20 9:42 ` Sebastian Andrzej Siewior [this message]
2022-06-21 15:27 ` Jinpu Wang
2022-06-22 6:43 ` Sebastian Andrzej Siewior
2022-06-22 6:56 ` Jinpu Wang
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=YrBA7ysAif4I9nPv@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=haris.iqbal@ionos.com \
--cc=jgg@ziepe.ca \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®