From: Cedar Maxwell <cedarmaxwell@mac.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
Finn Thain <fthain@linux-m68k.org>
Cc: Stan Johnson <userm57@yahoo.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] powerpc: Add reloc_offset() to font bitmap pointer used for bootx_printf()
Date: Sun, 18 Jan 2026 12:41:42 -0600 [thread overview]
Message-ID: <4c70fe51-56c3-4292-9eda-f0f4535718fe@mac.com> (raw)
In-Reply-To: <176680916368.22434.818943585854783800.b4-ty@linux.ibm.com>
Maddy (and everyone else),
Thank you all for your hard work in solving this issue!
Cedar Maxwell
On 12/26/25 10:23 PM, Madhavan Srinivasan wrote:
> On Mon, 10 Nov 2025 10:30:22 +1100, Finn Thain wrote:
>> Since Linux v6.7, booting using BootX on an Old World PowerMac produces
>> an early crash. Stan Johnson writes, "the symptoms are that the screen
>> goes blank and the backlight stays on, and the system freezes (Linux
>> doesn't boot)."
>>
>> Further testing revealed that the failure can be avoided by disabling
>> CONFIG_BOOTX_TEXT. Bisection revealed that the regression was caused by
>> a change to the font bitmap pointer that's used when btext_init() begins
>> painting characters on the display, early in the boot process.
>>
>> [...]
> Applied to powerpc/fixes.
>
> [1/1] powerpc: Add reloc_offset() to font bitmap pointer used for bootx_printf()
> https://git.kernel.org/powerpc/c/b94b73567561642323617155bf4ee24ef0d258fe
>
> cheers
prev parent reply other threads:[~2026-01-18 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 23:30 [PATCH v2] powerpc: Add reloc_offset() to font bitmap pointer used for bootx_printf() Finn Thain
2025-11-12 11:38 ` Christophe Leroy
2025-12-09 21:41 ` Finn Thain
2025-12-10 3:59 ` Madhavan Srinivasan
2025-12-27 4:23 ` Madhavan Srinivasan
2026-01-18 18:41 ` Cedar Maxwell [this message]
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=4c70fe51-56c3-4292-9eda-f0f4535718fe@mac.com \
--to=cedarmaxwell@mac.com \
--cc=benh@kernel.crashing.org \
--cc=chleroy@kernel.org \
--cc=fthain@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=stable@vger.kernel.org \
--cc=userm57@yahoo.com \
/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