diff options
| author | Parth Pancholi <parth.pancholi@toradex.com> | 2024-02-29 13:10:07 +0100 |
|---|---|---|
| committer | Parth Pancholi <parth.pancholi@toradex.com> | 2024-02-29 15:32:16 +0100 |
| commit | 327470f20734fb936d6a4017e3af3ef5228b8473 (patch) | |
| tree | 2c1109451e9f6a7d42bd3a8310286ca67661a602 | |
| parent | afba0bd75a7b2c8c8dd28a9051362c9bc04255e7 (diff) | |
linux-toradex-upstream: defconfig: modify ARCH_FORCE_MAX_ORDER
From kernel version 6.4.y on-wards [1], the range of memory page
orders which the user can ask from buddy allocator is changed to
0..MAX_ORDER. Previously, for older kernel versions (< 6.4.y),
this range was 0..MAX_ORDER-1.
This change resolves OOM killer issue on Colibri iMX6 (256MB RAM)
modules with the latest mainline kernel >= 6.4.y.
[1] - commit 23baf831a32c ("mm, treewide: redefine MAX_ORDER sanely")
Related-to: ELB-5316
Signed-off-by: Parth Pancholi <parth.pancholi@toradex.com>
| -rw-r--r-- | recipes-kernel/linux/linux-toradex-upstream/defconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/recipes-kernel/linux/linux-toradex-upstream/defconfig b/recipes-kernel/linux/linux-toradex-upstream/defconfig index d3ef1ee..77b3905 100644 --- a/recipes-kernel/linux/linux-toradex-upstream/defconfig +++ b/recipes-kernel/linux/linux-toradex-upstream/defconfig @@ -26,7 +26,7 @@ CONFIG_SOC_IMX7D=y CONFIG_SMP=y CONFIG_ARM_PSCI=y CONFIG_HIGHMEM=y -CONFIG_ARCH_FORCE_MAX_ORDER=14 +CONFIG_ARCH_FORCE_MAX_ORDER=13 CONFIG_CMDLINE="noinitrd console=ttymxc0,115200" CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_STAT=y |