From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id D5A9BC433F5 for ; Thu, 26 May 2022 17:15:22 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 2BE778D0003; Thu, 26 May 2022 13:15:22 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 2457B8D0002; Thu, 26 May 2022 13:15:22 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 0E8C08D0003; Thu, 26 May 2022 13:15:22 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 00E478D0002 for ; Thu, 26 May 2022 13:15:21 -0400 (EDT) Received: from smtpin10.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id BEDFB20727 for ; Thu, 26 May 2022 17:15:21 +0000 (UTC) X-FDA: 79508545242.10.A235737 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by imf21.hostedemail.com (Postfix) with ESMTP id C432C1C000A for ; Thu, 26 May 2022 17:15:08 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 59A58B82176; Thu, 26 May 2022 17:15:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 001E9C385A9; Thu, 26 May 2022 17:15:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1653585318; bh=QMMztxLvKJQWf7a0QkWnkoIuFYS9B45HbLCHT33oUGA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=o6KsTMAVGwX87LSuiavLr6WSB3qGGIueBSUASPi5xUwLMr70bFOixSwB+gclDYbZc dlHxzE3MNxdoRknxDvlLzcm2h3729/zkFV3g/mOZjL00BptFVjgsuLMWszZTiE+/h6 swmoy5rmC73E0U7Pnr2P1b8Z7Zxq5UU6PNmd4VrU= Date: Thu, 26 May 2022 10:15:17 -0700 From: Andrew Morton To: Michael Walle Cc: linux-mm@kvack.org, Zi Yan Subject: Re: cma: cma_alloc: reserved: alloc failed, req-size: 128 pages, ret: -16 Message-Id: <20220526101517.c5fe59edda4ab2d6e58adf00@linux-foundation.org> In-Reply-To: <90e0e68697e5377e0d3f320c0d126a27@walle.cc> References: <90e0e68697e5377e0d3f320c0d126a27@walle.cc> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Stat-Signature: 9ktracqdj8ym3qj4eayqsyp5jxow8edg X-Rspam-User: Authentication-Results: imf21.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=o6KsTMAV; dmarc=none; spf=pass (imf21.hostedemail.com: domain of akpm@linux-foundation.org designates 145.40.68.75 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: C432C1C000A X-HE-Tag: 1653585308-702150 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, 26 May 2022 17:06:08 +0200 Michael Walle 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.