From: "Michel Dänzer" <michel@daenzer.net>
To: Alex Deucher <alexdeucher@gmail.com>,
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Hillf Danton <hdanton@sina.com>,
Harry Wentland <harry.wentland@amd.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Memory Management List <linux-mm@kvack.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
Dave Airlie <airlied@gmail.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>
Subject: Re: The issue with page allocation 5.3 rc1-rc2 (seems drm culprit here)
Date: Thu, 8 Aug 2019 10:12:59 +0200 [thread overview]
Message-ID: <6d5110ab-6539-378d-f643-0a1d4cf0ff73@daenzer.net> (raw)
In-Reply-To: <CADnq5_O08v3_NUZ_zUZJFYwv_tUY7TFFz2GGudqgWEX6nh5LFA@mail.gmail.com>
On 2019-08-08 7:31 a.m., Alex Deucher wrote:
> On Wed, Aug 7, 2019 at 11:49 PM Mikhail Gavrilov
> <mikhail.v.gavrilov@gmail.com> wrote:
>>
>> Unfortunately error "gnome-shell: page allocation failure: order:4,
>> mode:0x40cc0(GFP_KERNEL|__GFP_COMP),
>> nodemask=(null),cpuset=/,mems_allowed=0" still happens even with
>> applying this patch.
>
> I think we can just drop the kmalloc altogether. How about this patch?
Memory allocated by kvz/malloc needs to be freed with kvfree.
--
Earthling Michel Dänzer | https://www.amd.com
Libre software enthusiast | Mesa and X developer
next prev parent reply other threads:[~2019-08-08 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190806014830.7424-1-hdanton@sina.com>
2019-08-08 3:48 ` The issue with page allocation 5.3 rc1-rc2 (seems drm culprit here) Mikhail Gavrilov
2019-08-08 5:31 ` Alex Deucher
2019-08-08 8:12 ` Michel Dänzer [this message]
2019-08-08 14:26 ` Alex Deucher
2019-08-09 18:55 ` Mikhail Gavrilov
2019-08-10 16:08 ` Mikhail Gavrilov
[not found] <20190805032114.8740-1-hdanton@sina.com>
2019-08-05 17:14 ` Mikhail Gavrilov
2019-08-04 22:23 Mikhail Gavrilov
2019-08-05 1:03 ` Dave Airlie
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=6d5110ab-6539-378d-f643-0a1d4cf0ff73@daenzer.net \
--to=michel@daenzer.net \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=airlied@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).