linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Bruno Goncalves <bgoncalv@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Sudeep Holla <sudeep.holla@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	CKI Project <cki-project@redhat.com>
Subject: Re: [5.19.0] [aarch64] WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:5407 __alloc_pages+0x1a0/0x290
Date: Fri, 5 Aug 2022 14:59:55 +0100	[thread overview]
Message-ID: <20220805135955.5to2bm6ou35p5zsy@bogus> (raw)
In-Reply-To: <CA+QYu4rPbfH-4wNR06Vn=31RCGKFFEB-KRskn52Jtig_UugYzg@mail.gmail.com>

On Fri, Aug 05, 2022 at 11:47:57AM +0200, Bruno Goncalves wrote:
> Hello,
> 
> Since commit "c1c76700a0d6" we started to hit the following call trace
> on aarch64 VMs when looking at journalctl log
>
> kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072
> bytes, linear)
> kernel: ACPI PPTT: No PPTT table found, CPU and cache topology may be inaccurate
> kernel: ------------[ cut here ]------------
> kernel: WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:5407 __alloc_pages+0x1a0/0x290
> kernel: Modules linked in:
> kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.19.0 #1
> kernel: pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> kernel: pc : __alloc_pages+0x1a0/0x290
> kernel: lr : alloc_page_interleave+0x24/0xbc
> kernel: sp : ffff80000803bb90
> kernel: x29: ffff80000803bb90 x28: 0000000000000000 x27: 0000000000000000
> kernel: x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000
> kernel: x23: 000000000000001e x22: 0000000000000000 x21: 000000000000001e
> kernel: x20: 000000000000001e x19: 0000000000040b20 x18: 0000000000000014
> kernel: x17: 6e69206562207961 x16: 6d2079676f6c6f70 x15: 6f74206568636163
> kernel: x14: 20646e6120555043 x13: 6574617275636361 x12: 6e69206562207961
> kernel: x11: 6d2079676f6c6f70 x10: 6f74206568636163 x9 : ffffa4f6617fd5e8
> kernel: x8 : ffffa4f663ed0440 x7 : 0000000000000007 x6 : 0000000000000000
> kernel: x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
> kernel: x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffa4f663c53532
> kernel: Call trace:
> kernel:  __alloc_pages+0x1a0/0x290
> kernel:  alloc_page_interleave+0x24/0xbc
> kernel:  alloc_pages+0x10c/0x16c
> kernel:  kmalloc_order+0x3c/0xc0
> kernel:  kmalloc_order_trace+0x38/0x130
> kernel:  __kmalloc+0x2e8/0x350
> kernel:  detect_cache_attributes+0x9c/0x110
> kernel:  update_siblings_masks+0x34/0x270
> kernel:  store_cpu_topology+0x7c/0xc0
> kernel:  smp_prepare_cpus+0x34/0x108
> kernel:  kernel_init_freeable+0x108/0x1b8
> kernel:  kernel_init+0x30/0x150
> kernel:  ret_from_fork+0x10/0x20
> kernel: ---[ end trace 0000000000000000 ]---
> kernel: Early cacheinfo failed, ret = -12
> kernel: cblist_init_generic: Setting adjustable number of callback queues.
> kernel: cblist_init_generic: Setting shift to 2 and lim to 1.
>

Thanks for the report. I will see if I can reproduce by forcing the absence
of PPTT which is something I haven't tested after I fixed hotplug issues
reported with my changes.

--
Regards,
Sudeep

  parent reply	other threads:[~2022-08-05 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  9:47 [5.19.0] [aarch64] WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:5407 __alloc_pages+0x1a0/0x290 Bruno Goncalves
2022-08-05 12:56 ` Mark Rutland
2022-08-05 13:28   ` Bruno Goncalves
2022-08-05 13:59 ` Sudeep Holla [this message]
2022-08-05 15:08   ` Sudeep Holla
2022-08-05 18:38     ` Bruno Goncalves

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=20220805135955.5to2bm6ou35p5zsy@bogus \
    --to=sudeep.holla@arm.com \
    --cc=bgoncalv@redhat.com \
    --cc=cki-project@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).