From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Walle <michael@walle.cc>
Cc: linux-mm@kvack.org, Zi Yan <ziy@nvidia.com>
Subject: Re: cma: cma_alloc: reserved: alloc failed, req-size: 128 pages, ret: -16
Date: Thu, 26 May 2022 10:15:17 -0700 [thread overview]
Message-ID: <20220526101517.c5fe59edda4ab2d6e58adf00@linux-foundation.org> (raw)
In-Reply-To: <90e0e68697e5377e0d3f320c0d126a27@walle.cc>
On Thu, 26 May 2022 17:06:08 +0200 Michael Walle <michael@walle.cc> wrote:
> Hi,
>
> Since the next-20220526 I'm getting the following error during boot:
> cma: cma_alloc: reserved: alloc failed, req-size: 128 pages, ret: -16
>
> E.g. on the following arm64 board:
> https://lavalab.kontron.com/scheduler/job/121315
>
> But initially I've noticed it on an arm board, which isn't
> in kernelci yet:
> https://pastebin.com/raw/JY2nFJjT
> (Ignore the subsequent i2c kernel oops, that seems to be
> a bug in the xdma driver).
>
> next-20220524 was still alright (not sure what has happened
> to next-20220525):
> https://lavalab.kontron.com/scheduler/job/120496
>
> Bisect of mm-everything..v5.18-rc4 is currently running but
> takes a while. Maybe anyone has an idea what goes wrong here?
Please try reverting 88ee134320b8311 ("mm: fix a potential infinite
loop in start_isolate_page_range()").
Is a real bummer. That was v11 of the patchset, it was in -next for a
month. The day before the merge window opens, bug turns up and it
seems that the attempt to fix the bug added a new one. Hopefully Zi Yan
will be able to plug this one soon.
next prev parent reply other threads:[~2022-05-26 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 15:06 cma: cma_alloc: reserved: alloc failed, req-size: 128 pages, ret: -16 Michael Walle
2022-05-26 17:15 ` Andrew Morton [this message]
2022-05-26 20:15 ` Zi Yan
2022-05-26 21:05 ` Michael Walle
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=20220526101517.c5fe59edda4ab2d6e58adf00@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=michael@walle.cc \
--cc=ziy@nvidia.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).