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 CD39CC433F5 for ; Thu, 26 May 2022 21:05:39 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 49B478D0003; Thu, 26 May 2022 17:05:39 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 445CB8D0002; Thu, 26 May 2022 17:05:39 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 35A5F8D0003; Thu, 26 May 2022 17:05:39 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 2736F8D0002 for ; Thu, 26 May 2022 17:05:39 -0400 (EDT) Received: from smtpin13.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id E87E2353B9 for ; Thu, 26 May 2022 21:05:38 +0000 (UTC) X-FDA: 79509125556.13.602EA31 Received: from ssl.serverraum.org (ssl.serverraum.org [176.9.125.105]) by imf09.hostedemail.com (Postfix) with ESMTP id C341814003A for ; Thu, 26 May 2022 21:05:24 +0000 (UTC) Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 6ACEA2223B; Thu, 26 May 2022 23:05:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1653599135; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yPsdBA118AhJrEdaA896W2WpjBzPdwIzPdD7h6W+YjE=; b=kszHeXUy8sI0ydGw5UW5Ycs9/x1fOx2V8JaytfIQnAFdOQ6zfGmaoag87roMmPrf6jFZMA hc9rYxzT+/wNihjYmSxnBH4GksiF7ZsZ+oJTQx51c5zJoRc3OR6dysRrsk6Ef2dl+joqC7 fo2/y4a2miMm6G6iDqBCWxLngGf8Q7s= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 26 May 2022 23:05:35 +0200 From: Michael Walle To: Zi Yan Cc: Andrew Morton , linux-mm@kvack.org Subject: Re: cma: cma_alloc: reserved: alloc failed, req-size: 128 pages, ret: -16 In-Reply-To: <2228808C-0FF4-47C2-82CE-9F6F3BA85232@nvidia.com> References: <90e0e68697e5377e0d3f320c0d126a27@walle.cc> <20220526101517.c5fe59edda4ab2d6e58adf00@linux-foundation.org> <2228808C-0FF4-47C2-82CE-9F6F3BA85232@nvidia.com> User-Agent: Roundcube Webmail/1.4.13 Message-ID: <8ca048ca8b547e0dd1c95387ee05c23d@walle.cc> X-Sender: michael@walle.cc Authentication-Results: imf09.hostedemail.com; dkim=pass header.d=walle.cc header.s=mail2016061301 header.b=kszHeXUy; dmarc=none; spf=pass (imf09.hostedemail.com: domain of michael@walle.cc designates 176.9.125.105 as permitted sender) smtp.mailfrom=michael@walle.cc X-Rspam-User: X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: C341814003A X-Stat-Signature: ec5eeorw6kq15uz1ow6t9w6k4sq6bx5j X-HE-Tag: 1653599124-255719 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000615, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hi, Am 2022-05-26 22:15, schrieb Zi Yan: > On 26 May 2022, at 13:15, Andrew Morton wrote: > >> 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()"). Thanks for the quick reply. I can confirm this is the culprit. >> 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. > > Hi Michael, > > The patch from this link should fix it: > https://lore.kernel.org/linux-mm/8C74B0BA-3C69-46EE-8C14-0CE6787D0B65@nvidia.com/. > Please give it a try. I can also confirm this is fixing it. You can add my Tested-by: Michael Walle -michael