From: Damian Dudycz <damiandudycz@yahoo.com>
To: linux-mm@kvack.org
Cc: sam@gentoo.org, holger@applied-asynchrony.com, kernel@gentoo.org,
hannes@cmpxchg.org
Subject: OOMs on PS3 since kernel 6.9-rc4
Date: Tue, 24 Sep 2024 22:52:28 +0200 [thread overview]
Message-ID: <7CE7C8BC-D728-4A10-BD8F-15293D7CF312@yahoo.com> (raw)
In-Reply-To: <7CE7C8BC-D728-4A10-BD8F-15293D7CF312.ref@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2480 bytes --]
I'm running Gentoo on the PlayStation 3 console (PPC64BE CPU), using custom
firmware (OtherOS++) feature.
Upgrading from 6.6 to 6.10, I have noticed that OOM kills started during long
and intense processes, like compiling code or extracting a large archive.
The OOM usually occurs after about 10-20 minutes of for example
compiling the gentoo-kernel package.
This system has limited amount of RAM (256MB) and there's possibility to use
another 256MB of VRam as a fast swap device. Besides that, there's also
standard swap partition of 4GB enabled. I bisected with vanilla upstream sources
with the exception of some irrelevant patches mentioned at the end.
After bisecting, I have found that the issue first started to appear in commit
c0cd6f557b9090525d288806cccbc73440ac235a (build 6.9.0-rc4-test)
(titled: "page_alloc: fix freelist movement during block conversion").
https://github.com/torvalds/linux/commit/c0cd6f557b9090525d288806cccbc73440ac235a
Unfortunately, it doesn't revert cleanly on 6.11 so I couldn't test that.
# Files and directories:
- patches: contains patches applied to kernel when preparing a test build. These are working with version 6.9
- config: kernel config used
- bisect.txt: log from bisecting process
- dmesg.txt: log from dmesg after issue occurred
- c0cd6f557b9090525d288806cccbc73440ac235a.patch: diff from commit that introduced the issue
- proc - Collection of files from /proc, before, after and during test. („During" was always taken 5 minutes after test was started).
- 6.9.0-rc3-test-dirty - working version, issue didn't happened.
- 6.9.0-rc4-test-00116-gc0cd6f557b90-dirty - commit that introduced the issue, OOM occurred.
- 6.11.0-test-dirty - newer version of kernel, OOM still occurred.
# Patches:
In order for kernel to work on the PS3 using OtherOS++, some patches are
required. I reduced the number of patches during testing, only to the ones
that are essential to boot correctly. The patches I have used are in "patches"
directory.
These are used mainly to enable linux to use disk regions that are
used for linux and I doubt they have any impact on the issue, but I'm adding them
in case this needs verification.
There are also 2 disabled patches related to page allocation, that I have left there,
but these were not used in tests, as they don't affect the result in this situation,
I'm leaving them just in case.
Mentioned logs and files are in attached tarball.
[-- Attachment #2: files-linux-6.9.0-rc4-test.tar.xz --]
[-- Type: application/x-xz, Size: 308736 bytes --]
next parent reply other threads:[~2024-09-24 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7CE7C8BC-D728-4A10-BD8F-15293D7CF312.ref@yahoo.com>
2024-09-24 20:52 ` Damian Dudycz [this message]
2024-09-25 17:20 ` Johannes Weiner
2024-09-25 17:43 ` Damian Dudycz
2024-09-26 7:00 ` Damian Dudycz
2024-09-26 10:34 ` Johannes Weiner
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=7CE7C8BC-D728-4A10-BD8F-15293D7CF312@yahoo.com \
--to=damiandudycz@yahoo.com \
--cc=hannes@cmpxchg.org \
--cc=holger@applied-asynchrony.com \
--cc=kernel@gentoo.org \
--cc=linux-mm@kvack.org \
--cc=sam@gentoo.org \
/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