From: Sam James <sam@gentoo.org>
To: Peter Zijlstra <peterz@infradead.org>,
Greg KH <gregkh@linuxfoundation.org>
Cc: matoro <matoro_mailinglist_kernel@matoro.tk>,
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>,
stable@vger.kernel.org
Subject: Re: Crash on boot with CONFIG_JUMP_LABEL in 6.10
Date: Wed, 31 Jul 2024 14:31:55 +0100 [thread overview]
Message-ID: <877cd1bsc4.fsf@gentoo.org> (raw)
In-Reply-To: <20240731110617.GZ33588@noisy.programming.kicks-ass.net> (Peter Zijlstra's message of "Wed, 31 Jul 2024 13:06:17 +0200")
[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]
Peter Zijlstra <peterz@infradead.org> writes:
> 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
Greg, I see tglx's jump_label fix is queued for 6.10.3 but this one
isn't as it came too late. Is there any chance of chucking it in? It's
pretty nasty.
thanks,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next parent reply other threads:[~2024-07-31 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <096cad5aada514255cd7b0b9dbafc768@matoro.tk>
[not found] ` <bebe64f6-b1e1-4134-901c-f911c4a6d2e6@bell.net>
[not found] ` <11e13a9d-3942-43a5-b265-c75b10519a19@bell.net>
[not found] ` <cb2c656129d3a4100af56c74e2ae3060@matoro.tk>
[not found] ` <20240731110617.GZ33588@noisy.programming.kicks-ass.net>
2024-07-31 13:31 ` Sam James [this message]
2024-07-31 13:41 ` Crash on boot with CONFIG_JUMP_LABEL in 6.10 Greg KH
2024-07-31 17:00 ` Sam James
2024-08-01 1:12 ` matoro
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=877cd1bsc4.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=dave.anglin@bell.net \
--cc=dave@parisc-linux.org \
--cc=deller@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
/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