On Wed 2025-10-22 19:56:45, Venkat Rao Bagalkote wrote:

On 22/10/25 6:36 pm, Petr Mladek wrote:

quoted

On Wed 2025-10-22 17:36:18, Venkat Rao Bagalkote wrote:

quoted

On 22/10/25 1:52 pm, Venkat Rao Bagalkote wrote:

quoted

Greetings!!!


IBM CI has reported kernel boot warnings with next-20251022 kernel. I
see there are couple of warnings hit and eventually system boots to
emergency mode.

With the identified first bad commit, is casuing the kernel to boot to
emergency mode. I reverted the bad commit and built the kernel, then kernel
is booting fine, but with boot warnings.

I guess that it is the same problem which should get fixed by the patch
https://lore.kernel.org/r/e52ee3edf32874da645a9e037a7d77c69893a22a.1760982784.git.jpoimboe@kernel.org (local)

Thank you Petr, for pointing to the fix patch. It fixes the kernel booting
to emergency mode.

Great.

But boot warning still persists.

I looks like another problem. I would expect that it is in
the ftrace code, either in the generic or arch-specific part.

I would suggest to add people proposed by:

$> ./scripts/get_maintainer.pl arch/powerpc/kernel/trace/ftrace.c
Steven Rostedt [off-list ref] (maintainer:FUNCTION HOOKS (FTRACE))
Masami Hiramatsu [off-list ref] (maintainer:FUNCTION HOOKS (FTRACE))
Mark Rutland [off-list ref] (reviewer:FUNCTION HOOKS (FTRACE))
Madhavan Srinivasan [off-list ref] (maintainer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Michael Ellerman [off-list ref] (maintainer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Nicholas Piggin [off-list ref] (reviewer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Christophe Leroy [off-list ref] (reviewer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
linux-kernel@vger.kernel.org (open list:FUNCTION HOOKS (FTRACE))
linux-trace-kernel@vger.kernel.org (open list:FUNCTION HOOKS (FTRACE))
linuxppc-dev@lists.ozlabs.org (open list:LINUX FOR POWERPC (32-BIT AND 64-BIT))
LINUX FOR POWERPC (32-BIT AND 64-BIT) status: Supported

into the original message with the backtrace. Or maybe, send it
once again and mention just the WARNING. The boot to the emergency
mode has been already solved...

Best Regards,
Petr