[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220905111832.73nqtlzpiuwpj7lx@houat>
Date: Mon, 5 Sep 2022 13:18:32 +0200
From: Maxime Ripard <maxime@...no.tech>
To: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Arnd Bergmann <arnd@...db.de>,
Olof Johansson <olof@...om.net>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Daniel Vetter <daniel.vetter@...el.com>,
David Airlie <airlied@...ux.ie>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Vlastimil Babka <vbabka@...e.cz>,
Roman Gushchin <roman.gushchin@...ux.dev>
Cc: Martin Roukala <martin.roukala@...uf.org>, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
dri-devel@...ts.freedesktop.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: RaspberryPi4 Panic in net_ns_init()
On Wed, Aug 31, 2022 at 04:42:05PM +0200, Maxime Ripard wrote:
> Sorry for the fairly broad list of recipients, I'm not entirely sure
> where the issue lies exactly, and it seems like multiple areas are
> involved.
>
> Martin reported me an issue discovered with the VC4 DRM driver that
> would prevent the RaspberryPi4 from booting entirely. At boot, and
> apparently before the console initialization, the board would just die.
>
> It first appeared when both DYNAMIC_DEBUG and DRM_VC4 were built-in. We
> started to look into what configuration would trigger it.
>
> It looks like a good reproducer is:
>
> ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make -j18 defconfig mod2yesconfig
> ./scripts/config -e CONFIG_DYNAMIC_DEBUG
> ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make -j18 olddefconfig
Interestingly, this was making the kernel Image cross the 64MB boundary.
I've compiled the same configuration but with -Os, and then tried to
boot the failing configuration with U-Boot instead of the RaspberryPi
firmware, and both of them worked. I guess that leaves us with a
bootloader bug, and nothing related to Linux after all.
Sorry for the noise,
Maxime
Powered by blists - more mailing lists