[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 8 Aug 2019 10:26:20 -0400
From: Alex Deucher <alexdeucher@...il.com>
To: Michel Dänzer <michel@...nzer.net>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>,
Hillf Danton <hdanton@...a.com>,
Dave Airlie <airlied@...il.com>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
amd-gfx list <amd-gfx@...ts.freedesktop.org>,
Linux Memory Management List <linux-mm@...ck.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
"Deucher, Alexander" <Alexander.Deucher@....com>,
Harry Wentland <harry.wentland@....com>,
"Koenig, Christian" <Christian.Koenig@....com>
Subject: Re: The issue with page allocation 5.3 rc1-rc2 (seems drm culprit here)
On Thu, Aug 8, 2019 at 4:13 AM Michel Dänzer <michel@...nzer.net> wrote:
>
> 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@...il.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.
>
Yup, good catch. Updated patch attached.
Alex
View attachment "0001-drm-amd-display-use-kvmalloc-for-dc_state-v2.patch" of type "text/x-patch" (1915 bytes)
Powered by blists - more mailing lists