From: Petr Mladek <pmladek@suse.com>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>,
joe.lawrence@redhat.com, Naveen N Rao <naveen@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
jpoimboe@kernel.org
Subject: Re: [next-20251022] Kernel Boot Warnings at arch/powerpc/kernel/trace/ftrace.c:234
Date: Wed, 22 Oct 2025 15:06:36 +0200 [thread overview]
Message-ID: <aPjW3P2AU7L71S-s@pathway.suse.cz> (raw)
In-Reply-To: <cdf7c458-b28f-4657-8708-1f820369baa6@linux.ibm.com>
On Wed 2025-10-22 17:36:18, Venkat Rao Bagalkote wrote:
>
> On 22/10/25 1:52 pm, Venkat Rao Bagalkote wrote:
> > 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
Best Regards,
Petr
next prev parent reply other threads:[~2025-10-22 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 8:22 [next-20251022] Kernel Boot Warnings at arch/powerpc/kernel/trace/ftrace.c:234 Venkat Rao Bagalkote
2025-10-22 8:26 ` Venkat Rao Bagalkote
2025-10-22 12:06 ` Venkat Rao Bagalkote
2025-10-22 13:06 ` Petr Mladek [this message]
2025-10-22 14:26 ` Venkat Rao Bagalkote
2025-10-23 9:12 ` Petr Mladek
2025-10-29 18:12 ` Hari Bathini
2025-10-30 2:06 ` Josh Poimboeuf
2025-10-30 12:39 ` Hari Bathini
2025-10-31 1:07 ` Josh Poimboeuf
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=aPjW3P2AU7L71S-s@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=hbathini@linux.ibm.com \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=masahiroy@kernel.org \
--cc=naveen@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=venkat88@linux.ibm.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 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.