Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <f2176adc-cc2f-4752-2c7e-102b73b55696@leemhuis.info>
Date:   Sun, 14 May 2023 15:14:58 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.0
Reply-To: Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Kernel 6.4-rc1 ARM boot fails
Content-Language: en-US, de-DE
To:     Colin Foster <colin.foster@in-advantage.com>,
        Ard Biesheuvel <ardb@kernel.org>
Cc:     linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        Linus Walleij <linus.walleij@linaro.org>,
        "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
        Linux kernel regressions list <regressions@lists.linux.dev>
References: <ZFs6DNgzBHNarr6D@euler>
From:   "Linux regression tracking #adding (Thorsten Leemhuis)" 
        <regressions@leemhuis.info>
In-Reply-To: <ZFs6DNgzBHNarr6D@euler>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 10.05.23 08:30, Colin Foster wrote:
> 
> I just wanted to give a heads up. I tested 6.4-rc1 on a Beaglebone Black
> and kept getting boot hangs. A bisect led me to commit c76c6c4ecbec ("ARM:
> 9294/2: vfp: Fix broken softirq handling with instrumentation enabled").
>
> The dying message is "Run /sbin/init as init process"
> 
> I'm not sure if this has already been reported. I was able to revert this
> patch and confirm things work again.
> [...]

Thanks for the report. I know a fix is incoming, but to be sure the
issue doesn't fall through the cracks unnoticed, I'm adding it to
regzbot, the Linux kernel regression tracking bot:

#regzbot ^introduced c76c6c4ecbec
#regzbot title arm32: tons of different boot time errors
#regzbot ignore-activity
#regzbot monitor:
https://lore.kernel.org/all/000000000000d3001a05faf979c8@google.com/
#regzbot fix ARM: 9297/1: vfp: avoid unbalanced stack on 'success'
return path
#regzbot monitor:
https://lore.kernel.org/all/20230506161325.223362-1-ardb@kernel.org/


This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.