> On 6 Jul 2024, at 17:44, Reimar Döffinger <reimar.doeffin...@gmx.de> wrote: > >> On 6 Jul 2024, at 17:26, Reimar Döffinger <reimar.doeffin...@gmx.de> wrote: >> >>> On 6 Jul 2024, at 17:17, John Paul Adrian Glaubitz >>> <glaub...@physik.fu-berlin.de> wrote: >>> >>> Hi Reimar, >>> >>>> On Jul 6, 2024, at 5:09 PM, Reimar Döffinger <reimar.doeffin...@gmx.de> >>>> wrote: >>>> >>>> Hi! >>>> The newest 6.9 powerpc kernel build seems to be incompatible with >>>> OpenFirmware boot, >>>> so boot fails on my PowerPC macMini. >>>> The error message is >>>> "Error: You can't boot a kdump kernel from OF!" >>>> The error message seems not entirely accurate, it seems the issue is that >>>> CONFIG_PHYSICAL_START >>>> is no longer 0, which probably comes from >>>> CONFIG_CRASH_DUMP=y >>>> being set. >>>> Can this be reverted? >>> >>> Could you verify that this change actually fixes the problem? This would >>> save me some work. >> >> I checked the kernel source, the error message is under a if (PHYSICAL_START >> > 0), so that I am quite certain is the issue. >> Actually testing means compiling the kernel, which will take quite some >> while. > > I can at least confirm that unsetting CONFIG_CRASH_DUMP in menuconfig results > in CONFIG_PHYSICAL_START to revert to 0. > So it seems very likely that this single config setting is the root cause.
Taking a step back, can someone explain how CONFIG_CRASH_DUMP ended up enabled in the powerpc kernel? Looking at https://salsa.debian.org/kernel-team/linux/-/tree/master/debian?ref_type=heads it does not seem to be enabled. There is a changelog entry from 2018 that says [powerpc,ppc64el,ppc64] Enable CRASH_DUMP (Closes: #883432) But that seems just incorrect, that change only modified debian/config/kernelarch-powerpc/config-arch-64 So I am not sure it's intentional that this setting is enabled? Anyone understanding what happened there? Best regards, Reimar
