public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	Jack D <wm2vdghq@duck.com>
Subject: Re: Boot error since 6.9: Initramfs unpacking failed: invalid magic at start of compressed archive
Date: Mon, 15 Jul 2024 11:04:24 +0100	[thread overview]
Message-ID: <20240715100424.GA18686@willie-the-truck> (raw)
In-Reply-To: <1a61d10f-7974-4fb5-ada6-f2c40c55f2f7@leemhuis.info>

On Mon, Jul 15, 2024 at 08:24:04AM +0200, Thorsten Leemhuis wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker.
> 
> I noticed a report about a regression in bugzilla.kernel.org that a user
> bisected to the main ARM64 merge commit from the 6.9 cycle. So the real
> issue might be somewhere else, but some help would be appreciated. To
> quote from https://bugzilla.kernel.org/show_bug.cgi?id=219014 :
> 
> > Hi.
> > 
> > I'm marking as arm64 since git bisect identifies the first problematic commit as:
> >   6d75c6f40a03c97e1ecd683ae54e249abb9d922b
> > 
> > git bisect log is attached.
> > 
> > Any kernel tagged v6.9x and later fails to boot with the following error:
> > 
> > [    0.420154] Initramfs unpacking failed: invalid magic at start of compressed archive

^^^

My guess (based on times I've seen this sort of thing in the past) is
that the kernel binary grew in size and the broken bootloader is loading
the kernel over the initramfs instead of parsing the 'image_size' field
in the boot header.

Will


  reply	other threads:[~2024-07-15 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15  6:24 Boot error since 6.9: Initramfs unpacking failed: invalid magic at start of compressed archive Thorsten Leemhuis
2024-07-15 10:04 ` Will Deacon [this message]
     [not found] ` <37EBD2B9-3314-4F42-8DDB-5D08242959E0.1@smtp-inbound1.duck.com>
2024-07-18  4:08   ` wm2vdghq

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=20240715100424.GA18686@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=wm2vdghq@duck.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