From: Peter Zijlstra <peterz@infradead.org>
To: matoro <matoro_mailinglist_kernel@matoro.tk>
Cc: John David Anglin <dave.anglin@bell.net>,
Linux Parisc <linux-parisc@vger.kernel.org>,
Deller <deller@gmx.de>, John David Anglin <dave@parisc-linux.org>
Subject: Re: Crash on boot with CONFIG_JUMP_LABEL in 6.10
Date: Wed, 31 Jul 2024 13:06:17 +0200 [thread overview]
Message-ID: <20240731110617.GZ33588@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <cb2c656129d3a4100af56c74e2ae3060@matoro.tk>
On Tue, Jul 30, 2024 at 08:36:13PM -0400, matoro wrote:
> On 2024-07-30 09:50, John David Anglin wrote:
> > On 2024-07-30 9:41 a.m., John David Anglin wrote:
> > > On 2024-07-29 7:11 p.m., matoro wrote:
> > > > Hi all, just bumped to the newest mainline starting with 6.10.2
> > > > and immediately ran into a crash on boot. Fully reproducible,
> > > > reverting back to last known good (6.9.8) resolves the issue.
> > > > Any clue what's going on here?
> > > > I can provide full boot logs, start bisecting, etc if needed...
> > > 6.10.2 built and booted okay on my c8000 with the attached config.
> > > You could start
> > > with it and incrementally add features to try to identify the one
> > > that causes boot failure.
> > Oh, I have an experimental clocksource patch installed. You will need
> > to regenerate config
> > with "make oldconfig" to use the current timer code. Probably, this
> > would happen automatically.
> > >
> > > Your config would be needed to duplicate. Full boot log would also help.
> >
> > Dave
>
> Hi Dave, bisecting quickly revealed the cause here.
https://lkml.kernel.org/r/20240731105557.GY33588@noisy.programming.kicks-ass.net
next prev parent reply other threads:[~2024-07-31 11:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 23:11 Crash on booth with 6.10 matoro
2024-07-30 13:41 ` John David Anglin
2024-07-30 13:50 ` John David Anglin
2024-07-31 0:36 ` Crash on boot with CONFIG_JUMP_LABEL in 6.10 matoro
2024-07-31 11:06 ` Peter Zijlstra [this message]
2024-07-31 13:31 ` Sam James
2024-07-31 13:41 ` Greg KH
2024-07-31 17:00 ` Sam James
2024-08-01 1:12 ` matoro
2024-08-30 18:18 ` Crash on booth with 6.10 Christoph Biedl
2024-08-30 23:33 ` Helge Deller
2024-08-31 9:10 ` Helge Deller
2024-08-31 17:44 ` Christoph Biedl
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=20240731110617.GZ33588@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dave.anglin@bell.net \
--cc=dave@parisc-linux.org \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
/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