All of lore.kernel.org
 help / color / mirror / Atom feed
From: <markus.stockhausen@gmx.de>
To: <rppt@kernel.org>, <tglx@linutronix.de>
Cc: <linux-mm@kvack.org>, <linux-mips@vger.kernel.org>,
	<jelonek.jonas@gmail.com>,
	"'Chris Packham'" <Chris.Packham@alliedtelesis.co.nz>,
	<hauke@hauke-m.de>
Subject: HIGHMEM freeing patch breaks Realtek RTL930x builds
Date: Sat, 20 Dec 2025 09:57:40 +0100	[thread overview]
Message-ID: <00bc01dc718e$b4108af0$1c31a0d0$@gmx.de> (raw)

Hi,

sorry for being late on this topic but downstream OpenWrt just started
kernel
conversion from 6.12 to 6.18 these days. During preparation of the PR
https://github.com/openwrt/openwrt/pull/21181 we noticed that Realtek 
RTL930x soc based devices with more than 256MB (highmem) do not boot 
any longer. 

These are MIPS 34k 32bit multithreaded SoC with layout 
<0x00000000 0x10000000>, /* 256 MiB lowmem */
<0x20000000 0x10000000>; /* 256 MiB highmem */

Bisecting the issue gave " arch, mm: streamline HIGHMEM freeing" 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
?h=v6.15-rc1&id=6faea3422e3b4e8de44a55aa3e6e843320da66d2
as the first bad commit. This is back from the 6.15 times.

I have no real idea why removing mem_init_free_highmem() and letting
__free_memory_core() work on the whole memory range gives issues.

We are aligning to upstream very slowly and are still in need of 
downstream patches so here some additional info.

- Until now we never cared about FLATMEM/SPARSEMEM configs

- We are still using dedicated prom.c/setup.c for the devices
https://git.openwrt.org/?p=openwrt/openwrt.git;a=tree;f=target/linux/
realtek/files-6.12/arch/mips/rtl838x;hb=HEAD

Any idea or hint is appreciated.

Thanks in advance.

Markus





             reply	other threads:[~2025-12-20  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-20  8:57 markus.stockhausen [this message]
2025-12-28  9:54 ` HIGHMEM freeing patch breaks Realtek RTL930x builds Mike Rapoport
  -- strict thread matches above, loose matches on Subject: below --
2025-12-29 18:36 markus.stockhausen
2025-12-29 19:35 ` Mike Rapoport

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='00bc01dc718e$b4108af0$1c31a0d0$@gmx.de' \
    --to=markus.stockhausen@gmx.de \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=hauke@hauke-m.de \
    --cc=jelonek.jonas@gmail.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.