From: Peter Zijlstra <peterz@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: boot failure after merge of the tip tree
Date: Wed, 24 May 2023 11:34:54 +0200 [thread overview]
Message-ID: <20230524093454.GI4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230524154459.48cda184@canb.auug.org.au>
On Wed, May 24, 2023 at 03:44:59PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc
> pseries_le_defconfig) failed to boot like this:
>
> Built 1 zonelists, mobility grouping on. Total pages: 32736
> Policy zone: Normal
> mem auto-init: stack:all(zero), heap alloc:off, heap free:off
> Memory: 2027392K/2097152K available (17984K kernel code, 3328K rwdata, 14784K rodata, 6080K init, 1671K bss, 69760K reserved, 0K cma-reserved)
>
> *crickets*
>
> Bisected to commit
>
> f4ab23558310 ("slub: Replace cmpxchg_double()")
>
> I have reverted that commit (and the following one) for today.
Sorry about that; turns out I forgot to test the case where cmpxchg128
wasn't available.
Please see:
https://lkml.kernel.org/r/20230524093246.GP83892@hirez.programming.kicks-ass.net
As stated there, I'm going to zap tip/locking/core for a few days and
let this fixed version run through the robots again before re-instating
it.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: linux-next: boot failure after merge of the tip tree
Date: Wed, 24 May 2023 11:34:54 +0200 [thread overview]
Message-ID: <20230524093454.GI4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230524154459.48cda184@canb.auug.org.au>
On Wed, May 24, 2023 at 03:44:59PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc
> pseries_le_defconfig) failed to boot like this:
>
> Built 1 zonelists, mobility grouping on. Total pages: 32736
> Policy zone: Normal
> mem auto-init: stack:all(zero), heap alloc:off, heap free:off
> Memory: 2027392K/2097152K available (17984K kernel code, 3328K rwdata, 14784K rodata, 6080K init, 1671K bss, 69760K reserved, 0K cma-reserved)
>
> *crickets*
>
> Bisected to commit
>
> f4ab23558310 ("slub: Replace cmpxchg_double()")
>
> I have reverted that commit (and the following one) for today.
Sorry about that; turns out I forgot to test the case where cmpxchg128
wasn't available.
Please see:
https://lkml.kernel.org/r/20230524093246.GP83892@hirez.programming.kicks-ass.net
As stated there, I'm going to zap tip/locking/core for a few days and
let this fixed version run through the robots again before re-instating
it.
next prev parent reply other threads:[~2023-05-24 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 5:44 linux-next: boot failure after merge of the tip tree Stephen Rothwell
2023-05-24 5:44 ` Stephen Rothwell
2023-05-24 9:34 ` Peter Zijlstra [this message]
2023-05-24 9:34 ` Peter Zijlstra
2023-05-26 8:50 ` Ingo Molnar
2023-05-26 8:50 ` Ingo Molnar
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=20230524093454.GI4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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.