From: <markus.stockhausen@gmx.de>
To: "'Mike Rapoport'" <rppt@kernel.org>
Cc: <tglx@linutronix.de>, <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: AW: HIGHMEM freeing patch breaks Realtek RTL930x builds
Date: Mon, 29 Dec 2025 22:16:12 +0100 [thread overview]
Message-ID: <003f01dc7908$5d0266d0$17073470$@gmx.de> (raw)
In-Reply-To: <aVLX9yLmIBPzI0MQ@kernel.org>
Hi Mike,
> The successful boot disables highmem:
> [ 0.332305] Memory: 495640K/524288K available (8188K kernel code, 647K
rwdata, 1504K rodata, 9620K init, 244K bss, 27528K reserved, 0K
cma-reserved, 0K highmem)
>
> And the failing boot actually enables it:
> [ 0.332285] Memory: 495640K/524288K available (8188K kernel code, 647K
rwdata, 1504K rodata, 9620K init, 244K bss, 27528K reserved, 0K
cma-reserved, 262144K highmem)
>
> so I believe that the partial revert should help.
Interesting find. That is strange. On 6.12 (where everything
works) the 256MB highmem are detected properly.
[ 0.242252] Memory: 493784K/524288K available (8373K kernel code, 725K
rwdata, 1820K rodata, 10896K init, 248K bss, 29384K reserved, 0K
cma-reserved, 262144K highmem)
Additionally I identified some spooky highmem
initialization in vendors SDK prom.c. We never
used that before. I added bootlog+code snippet
to the github issue [1].
Just to be sure. Do you expect highmem to be still
detected/advertised with 6.15+? If yes I will bisect
where the highmem detection breaks prior to the
"suspicous" commit.
Markus
[1] https://github.com/openwrt/openwrt/issues/21323
next prev parent reply other threads:[~2025-12-29 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 18:36 markus.stockhausen
2025-12-29 19:35 ` Mike Rapoport
2025-12-29 21:16 ` markus.stockhausen [this message]
2025-12-30 15:31 ` AW: " markus.stockhausen
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='003f01dc7908$5d0266d0$17073470$@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox