From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Maxime Ripard <maxime@cerno.tech>
Cc: Phil Elwell <phil@raspberrypi.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>
Subject: Re: [BUG] bcm2711: bad_chained_irq in brcmstb_l2_intc_irq_handle
Date: Thu, 20 Jan 2022 13:38:08 -0800 [thread overview]
Message-ID: <8a040749-e4fa-8b9d-e3e9-377a1e6f27a0@gmail.com> (raw)
In-Reply-To: <dc990eae-506c-5f4e-efde-ec483c6f9aa9@i2se.com>
On 1/20/2022 1:23 PM, Stefan Wahren wrote:
> Hi,
>
> Am 20.01.22 um 20:48 schrieb Florian Fainelli:
>>
>> Can we get the full dump of the Device Tree that you are running with?
>> Something like:
>>
>> dtc -I fs /proc/device-tree -O dts > live.dts
>>
>> would be helpful to figure out what is going on here.
>
> sorry guys, i assumed that the Arch people know what they do. I figured
> out that they mixed the vendor DTB with the mainline kernel.
No worries, it's always good to be thrown debugging exercises :), glad
you figured it out.
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-01-20 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 17:26 [BUG] bcm2711: bad_chained_irq in brcmstb_l2_intc_irq_handle Stefan Wahren
2022-01-16 20:15 ` Florian Fainelli
2022-01-17 4:59 ` Florian Fainelli
2022-01-20 15:54 ` Maxime Ripard
2022-01-20 15:39 ` Maxime Ripard
2022-01-20 18:10 ` Stefan Wahren
2022-01-20 19:48 ` Florian Fainelli
2022-01-20 21:23 ` Stefan Wahren
2022-01-20 21:38 ` Florian Fainelli [this message]
2022-01-21 3:51 ` Florian Fainelli
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=8a040749-e4fa-8b9d-e3e9-377a1e6f27a0@gmail.com \
--to=f.fainelli@gmail.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--cc=stefan.wahren@i2se.com \
/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).