[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cc9ff9ea-1f2e-16e9-a612-2ad4521440a6@mupuf.org>
Date: Thu, 8 Sep 2022 11:14:29 +0300
From: Martin Roukala <martin.roukala@...uf.org>
To: Maxime Ripard <maxime@...no.tech>,
"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: 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 9/5/22 14:18, Maxime Ripard wrote:
> 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
Thanks a lot for figuring this out, Maxime! The idea to use -Os is much
nicer than what I was going for: padding a working kernel with 0s at the
end!
I unfortunately did not try to reproduce your success with u-boot, but
I'll get to it in the near future.
Thanks again to everyone involved for all the help and support!
Martin
Powered by blists - more mailing lists