From: "Michel Dänzer" <michel@daenzer.net>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
alexander.deucher@amd.com,
Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: amdgpu crashes on OOM
Date: Mon, 26 Oct 2020 12:03:46 +0100 [thread overview]
Message-ID: <81568253-518f-43b7-6b20-432f7dbd6c2b@daenzer.net> (raw)
In-Reply-To: <1603684905.h43s1t0y05.none@localhost>
On 2020-10-26 5:29 a.m., Alex Xu (Hello71) wrote:
> Hi,
>
> I frequently encounter OOM on my system, mostly due to my own fault.
> Recently, I noticed that not only does a swap storm happen and OOM
> killer gets invoked, but the graphics output freezes permanently.
> Checking the kernel messages, I see:
>
> kworker/u24:4: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null)
> CPU: 6 PID: 279469 Comm: kworker/u24:4 Tainted: G W 5.9.0-14732-g20b1adb60cf6 #2
> Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.20 06/18/2020
> Workqueue: events_unbound commit_work
> Call Trace:
> ? dump_stack+0x57/0x6a
> ? warn_alloc.cold+0x69/0xcd
> ? __alloc_pages_direct_compact+0xfb/0x116
> ? __alloc_pages_slowpath.constprop.0+0x9c2/0xc14
> ? __alloc_pages_nodemask+0x143/0x167
> ? kmalloc_order+0x24/0x64
> ? dc_create_state+0x1a/0x4d
> ? amdgpu_dm_atomic_commit_tail+0x1b19/0x227d
Looks like dc_create_state should use kvzalloc instead of kzalloc
(dc_state_free already uses kvfree).
order:5 means it's trying to allocate 32 physically contiguous pages,
which can be hard to fulfill even with lower memory pressure.
--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and X developer
next prev parent reply other threads:[~2020-10-26 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1603684905.h43s1t0y05.none.ref@localhost>
2020-10-26 4:29 ` amdgpu crashes on OOM Alex Xu (Hello71)
2020-10-26 11:03 ` Michel Dänzer [this message]
2020-10-26 14:34 ` Deucher, Alexander
2020-10-26 14:50 ` Alex Xu (Hello71)
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=81568253-518f-43b7-6b20-432f7dbd6c2b@daenzer.net \
--to=michel@daenzer.net \
--cc=alex_y_xu@yahoo.ca \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicholas.kazlauskas@amd.com \
--cc=sunpeng.li@amd.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).