linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	David Airlie <airlied@linux.ie>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Christoph Lameter <cl@linux.com>,
	Pekka Enberg <penberg@kernel.org>,
	David Rientjes <rientjes@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Roman Gushchin <roman.gushchin@linux.dev>
Cc: Martin Roukala <martin.roukala@mupuf.org>,
	netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: RaspberryPi4 Panic in net_ns_init()
Date: Mon, 5 Sep 2022 13:18:32 +0200	[thread overview]
Message-ID: <20220905111832.73nqtlzpiuwpj7lx@houat> (raw)
In-Reply-To: <20220831144205.iirdun6bf3j5v6q4@houat>

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


  reply	other threads:[~2022-09-05 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 14:42 Maxime Ripard
2022-09-05 11:18 ` Maxime Ripard [this message]
2022-09-08  8:14   ` Martin Roukala

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=20220905111832.73nqtlzpiuwpj7lx@houat \
    --to=maxime@cerno.tech \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=cl@linux.com \
    --cc=daniel.vetter@intel.com \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edumazet@google.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=martin.roukala@mupuf.org \
    --cc=netdev@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=pabeni@redhat.com \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=tzimmermann@suse.de \
    --cc=vbabka@suse.cz \
    --cc=will@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