From: Stefan Wahren <wahrenst@gmx.net>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
krzk+dt@kernel.org, Rob Herring <robh@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next-20240814: bcm2711-rpi-4-b boot failed
Date: Wed, 14 Aug 2024 18:19:50 +0200 [thread overview]
Message-ID: <da941b0e-8e29-4ff7-aff8-683da0aef8da@gmx.net> (raw)
In-Reply-To: <CA+G9fYv2M8tqwXQF5At4KmG3PFJoiv3D-4Tn_q87MfBvAqLmag@mail.gmail.com>
Hi Naresh,
Am 14.08.24 um 17:26 schrieb Naresh Kamboju:
> On Wed, 14 Aug 2024 at 20:54, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>> The arm64 kernel booting on bcm2711-rpi-4-b boot failed with today's Linux
>> next-20240814 tag. The boot failed with half boot log [1]
>>
>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>
>> GOOD: next-20240813
>> BAD: next-20240814
>>
>> The first investigation show the following to changes and I have reverted the
>> following two commits and the boot test is back to pass [2].
>>
>> $ git log --oneline next-20240813..next-20240814
>> arch/arm64/boot/dts/broadcom/
>> 6e7b99d720da6 ARM: dts: bcm271x: add missing properties to local_intc
>> eb81f43c901ff ARM: dts: bcm2837/bcm2712: adjust local intc node names
>>
> Anders bisected down to first bad commit as,
> 6e7b99d720da ("ARM: dts: bcm271x: add missing properties to local_intc")
thank you for the report and sorry about that mess. I don't why i was
under the impression they were harmless DT properties. I look into this,
so a revert is the proper solution for now.
Regards
next prev parent reply other threads:[~2024-08-14 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 15:24 Naresh Kamboju
2024-08-14 15:26 ` Naresh Kamboju
2024-08-14 16:19 ` Stefan Wahren [this message]
2024-08-14 19:48 ` Florian Fainelli
2024-08-14 20:50 ` Stefan Wahren
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=da941b0e-8e29-4ff7-aff8-683da0aef8da@gmx.net \
--to=wahrenst@gmx.net \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=robh@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
all inboxes | Powered by JetHome®