From: Ozgur Kara <ozgur@goosey.org>
To: Yin Guoyu <y04609127@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: Kernel panic - not syncing: System is deadlocked on memory
Date: Sun, 11 May 2025 12:08:34 +0000 [thread overview]
Message-ID: <01100196bf3f39fa-6a0efe25-8752-4c2b-8353-b259059ab2f9-000000@eu-north-1.amazonses.com> (raw)
In-Reply-To: <CAJNGr6ve_6o6drwe_+bRW6UU4Ew9EjaZYaBgx0JAQjYb+A8VSA@mail.gmail.com>
Yin Guoyu <y04609127@gmail.com>, 11 May 2025 Paz, 14:35 tarihinde şunu yazdı:
>
> Hi,
> When I test the Linux kernel (commit
> 38fec10eb60d687e30c8c6b5420d86e8149f7557), I encountered a kernel
> panic issue related to memory allocation, specifically in the
> alloc_pages_mpol function. The panic message indicates "System is
> deadlocked on memory," and the call trace points to
> __alloc_frozen_pages_noprof failing to allocate pages, leading to an
> OOM condition.
> The error originates in alloc_pages_mpol, which calls policy_nodemask
> to determine the nodemask and nid for memory allocation. The
> subsequent call to __alloc_frozen_pages_noprof fails when the system
> runs out of memory, with no swap available and no killable processes.
> This crash can be triggered by executing the provided C reproducer
> multiple times. The reproducer performs a series of system calls
> (e.g., file creation, perf_event_open, io_submit, and filesystem
> mounts), which likely stress the memory management system and expose
> the bug.
Hello,
did you open a bug for this?
https://bugzilla.kernel.org
And i'm not sure if this is a bug i gues you are using qemu and you
experienced OOM (out of memory) because there is no swap and physical
ram is completely full.
it gets killed while kernel is initializing.
[ 133.880979] Free swap = 0kB
[ 133.889391] Out of memory and no killable processes...
This was an expected kernel behavior when there was no swap.
Regards,
Ozgur
> This can be reproduced on:
> HEAD commit:
> 38fec10eb60d687e30c8c6b5420d86e8149f7557
> console output : https://pastebin.com/raw/T4dfWHSf
> kernel config : https://pastebin.com/raw/u0Efyj5P
> C reproducer : https://pastebin.com/raw/3hPqjF6M
>
>
>
next prev parent reply other threads:[~2025-05-11 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 11:35 Yin Guoyu
2025-05-11 12:07 ` Matthew Wilcox
2025-05-11 12:08 ` Ozgur Kara [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-11 9:33 yinguoyu
2025-05-11 9:08 尹国宇
2025-05-11 8:37 yinguoyu
2025-05-11 8:17 yinguoyu
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=01100196bf3f39fa-6a0efe25-8752-4c2b-8353-b259059ab2f9-000000@eu-north-1.amazonses.com \
--to=ozgur@goosey.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=y04609127@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