From: David Rientjes <rientjes@google.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: "Christian König" <christian.koenig@amd.com>,
ckoenig.leichtzumerken@gmail.com,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>
Subject: Re: [bug] 5.11-rc5 brought page allocation failure issue [ttm][amdgpu]
Date: Sat, 30 Jan 2021 17:03:37 -0800 (PST) [thread overview]
Message-ID: <e0c2c823-5f-efe8-cd87-6dd6cc33a33@google.com> (raw)
In-Reply-To: <4ce29a7e-f58a-aeb4-bef-34a7eada70d0@google.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Sat, 30 Jan 2021, David Rientjes wrote:
> On Sun, 31 Jan 2021, Mikhail Gavrilov wrote:
>
> > The 5.11-rc5 (git 76c057c84d28) brought a new issue.
> > Now the kernel log is flooded with the message "page allocation failure".
> >
> > Trace:
> > msedge:cs0: page allocation failure: order:10,
>
> Order-10, wow!
>
> ttm_pool_alloc() will start at order-10 and back off trying smaller orders
> if necessary. This is a regression introduced in
>
> commit bf9eee249ac2032521677dd74e31ede5429afbc0
> Author: Christian König <christian.koenig@amd.com>
> Date: Wed Jan 13 14:02:04 2021 +0100
>
> drm/ttm: stop using GFP_TRANSHUGE_LIGHT
>
> Namely, it removed the __GFP_NOWARN that we otherwise require. I'll send
> a patch in reply.
>
Looks like Michel Dänzer <michel@daenzer.net> already sent a patch that
should fix this:
https://lore.kernel.org/lkml/20210128095346.2421-1-michel@daenzer.net/
next prev parent reply other threads:[~2021-01-31 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 23:17 [bug] 5.11-rc5 brought page allocation failure issue [ttm][amdgpu] Mikhail Gavrilov
2021-01-31 1:01 ` David Rientjes
2021-01-31 1:03 ` David Rientjes [this message]
2021-02-03 13:22 ` Christian König
2021-02-06 18:17 ` Mikhail Gavrilov
2021-02-08 9:18 ` Christian König
2021-02-09 19:22 ` Mikhail Gavrilov
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=e0c2c823-5f-efe8-cd87-6dd6cc33a33@google.com \
--to=rientjes@google.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.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