From: Michael Ellerman <mpe@ellerman.id.au>
To: "Linux regression tracking #adding (Thorsten Leemhuis)"
<regressions@leemhuis.info>,
Christian Zigotzky <chzigotzky@xenosoft.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Rob Herring <robh@kernel.org>,
Darren Stevens <darren@stevens-zone.net>,
Linux kernel regressions list <regressions@lists.linux.dev>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Olof Johansson <olof@lixom.net>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1
Date: Mon, 08 May 2023 22:49:54 +1000 [thread overview]
Message-ID: <87ttwn56od.fsf@mail.lhotse> (raw)
In-Reply-To: <71f580c7-0890-b622-62c9-f58fa9537a90@leemhuis.info>
"Linux regression tracking #adding (Thorsten Leemhuis)"
<regressions@leemhuis.info> writes:
> [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.]
Patch is in testing.
https://lore.kernel.org/linuxppc-dev/20230505171816.3175865-1-robh@kernel.org/
cheers
> On 02.05.23 04:22, Christian Zigotzky wrote:
>> Hello,
>>
>> Our PASEMI Nemo board [1] doesn't boot with the PowerPC updates 6.4-1 [2].
>>
>> The kernel hangs right after the booting Linux via __start() @
>> 0x0000000000000000 ...
>>
>> I was able to revert the PowerPC updates 6.4-1 [2] with the following
>> command: git revert 70cc1b5307e8ee3076fdf2ecbeb89eb973aa0ff7 -m 1
>>
>> After a re-compiling, the kernel boots without any problems without the
>> PowerPC updates 6.4-1 [2].
>>
>> Could you please explain me, what you have done in the boot area?
>>
>> Please find attached the kernel config.
>
> Thanks for the report. 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 e4ab08be5b4902e5
> #regzbot title powerpc: boot issues on PASEMI Nemo board
> #regzbot ignore-activity
>
> 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.
next prev parent reply other threads:[~2023-05-08 12:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 2:22 [PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1 Christian Zigotzky
2023-05-02 8:17 ` Christophe Leroy
2023-05-02 9:28 ` Michael Ellerman
2023-05-03 15:46 ` Christian Zigotzky
2023-05-03 16:27 ` Christophe Leroy
2023-05-03 16:51 ` Rob Herring
2023-05-03 17:28 ` Christian Zigotzky
2023-05-03 17:44 ` Christian Zigotzky
2023-05-03 18:15 ` Rob Herring
2023-05-04 4:51 ` Michael Ellerman
2023-05-05 4:48 ` Christian Zigotzky
2023-05-05 14:19 ` Rob Herring
2023-05-08 11:29 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-05-08 12:49 ` Michael Ellerman [this message]
2023-05-08 13:15 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 12:58 ` Bagas Sanjaya
2023-05-08 13:17 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 13:20 ` Bagas Sanjaya
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=87ttwn56od.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--cc=rtd2@xtra.co.nz \
/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;
as well as URLs for NNTP newsgroup(s).