diff options
| author | Parth Pancholi <parth.pancholi@toradex.com> | 2024-04-02 13:10:34 +0200 |
|---|---|---|
| committer | Parth Pancholi <parth.pancholi@toradex.com> | 2024-04-02 14:18:19 +0200 |
| commit | 451c884e85be7b6897eb9d6985c59d5e49c5cf50 (patch) | |
| tree | 347643882de5def83af770111fc8a577fde5c8ed | |
| parent | 7f2144eff1ce34eeb7fdfb195f03c209b134cf0e (diff) | |
linux-toradex-upstream-6.6: 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-6.6/defconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/recipes-kernel/linux/linux-toradex-upstream-6.6/defconfig b/recipes-kernel/linux/linux-toradex-upstream-6.6/defconfig index 303a479..0bbb726 100644 --- a/recipes-kernel/linux/linux-toradex-upstream-6.6/defconfig +++ b/recipes-kernel/linux/linux-toradex-upstream-6.6/defconfig @@ -27,7 +27,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 |