* Re: Crash on boot with CONFIG_JUMP_LABEL in 6.10 [not found] ` <20240731110617.GZ33588@noisy.programming.kicks-ass.net> @ 2024-07-31 13:31 ` Sam James 2024-07-31 13:41 ` Greg KH 0 siblings, 1 reply; 4+ messages in thread From: Sam James @ 2024-07-31 13:31 UTC (permalink / raw) To: Peter Zijlstra, Greg KH Cc: matoro, John David Anglin, Linux Parisc, Deller, John David Anglin, stable [-- 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 --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Crash on boot with CONFIG_JUMP_LABEL in 6.10 2024-07-31 13:31 ` Crash on boot with CONFIG_JUMP_LABEL in 6.10 Sam James @ 2024-07-31 13:41 ` Greg KH 2024-07-31 17:00 ` Sam James 0 siblings, 1 reply; 4+ messages in thread From: Greg KH @ 2024-07-31 13:41 UTC (permalink / raw) To: Sam James Cc: Peter Zijlstra, matoro, John David Anglin, Linux Parisc, Deller, John David Anglin, stable On Wed, Jul 31, 2024 at 02:31:55PM +0100, Sam James wrote: > 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. What is the git id of this in Linus's tree? thanks, greg k-h ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Crash on boot with CONFIG_JUMP_LABEL in 6.10 2024-07-31 13:41 ` Greg KH @ 2024-07-31 17:00 ` Sam James 2024-08-01 1:12 ` matoro 0 siblings, 1 reply; 4+ messages in thread From: Sam James @ 2024-07-31 17:00 UTC (permalink / raw) To: Greg KH Cc: Peter Zijlstra, matoro, John David Anglin, Linux Parisc, Deller, John David Anglin, stable Greg KH <gregkh@linuxfoundation.org> writes: > On Wed, Jul 31, 2024 at 02:31:55PM +0100, Sam James wrote: >> 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. > > What is the git id of this in Linus's tree? Ah, you're right, it's not there. Sorry, I thought I'd seen it pulled. > > thanks, > > greg k-h ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Crash on boot with CONFIG_JUMP_LABEL in 6.10 2024-07-31 17:00 ` Sam James @ 2024-08-01 1:12 ` matoro 0 siblings, 0 replies; 4+ messages in thread From: matoro @ 2024-08-01 1:12 UTC (permalink / raw) To: Sam James Cc: Greg KH, Peter Zijlstra, John David Anglin, Linux Parisc, Deller, John David Anglin, stable On 2024-07-31 13:00, Sam James wrote: > Greg KH <gregkh@linuxfoundation.org> writes: > >> On Wed, Jul 31, 2024 at 02:31:55PM +0100, Sam James wrote: >>> 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. >> >> What is the git id of this in Linus's tree? > > Ah, you're right, it's not there. Sorry, I thought I'd seen it pulled. > >> >> thanks, >> >> greg k-h Hi Peter, sorry I'm not quite following, exactly what patches need to be applied to fix this? I checked out the thread you linked but it does not apply cleanly to 6.10. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-08-01 1:12 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 ` Crash on boot with CONFIG_JUMP_LABEL in 6.10 Sam James
2024-07-31 13:41 ` Greg KH
2024-07-31 17:00 ` Sam James
2024-08-01 1:12 ` matoro
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox