From: Dave Hansen <dave.hansen@intel.com>
To: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>, Ingo Molnar <mingo@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Ian Campbell <ijc@hellion.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org
Subject: Re: [tip: x86/build] x86/boot: Drop CRC-32 checksum and the build tool that generates it
Date: Fri, 11 Apr 2025 12:33:47 -0700 [thread overview]
Message-ID: <364ad671-5e5c-47c1-af22-34a7c481f8e3@intel.com> (raw)
In-Reply-To: <174138907883.14745.965399833848496586.tip-bot2@tip-bot2>
On 3/7/25 15:11, tip-bot2 for Ard Biesheuvel wrote:
> x86/boot: Drop CRC-32 checksum and the build tool that generates it
This is breaking really early boot for me across a whole bunch of i386
and 64-bit builds. I had to bisect it because this does not seem like
the kind of thing that would break the boot. It's either hanging the
kernel *really* early, or making KVM angry:
KVM internal error. Suberror: 1
extra data[0]: 0x0000000000000000
extra data[1]: 0x0000000000000030
extra data[2]: 0x0000000000000784
extra data[3]: 0x0000000000000000
extra data[4]: 0x0000000000000000
extra data[5]: 0x0000000000000000
emulation failure
EAX=00000000 EBX=00000000 ECX=00000000 EDX=00083238
ESI=00000000 EDI=00000000 EBP=00000000 ESP=0000fff5
EIP=00008300 EFL=00010002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
...
I'm going to go start backing out individual hunks like the
arch/x86/boot/compressed/vmlinux.lds.S changes, but I figured I'd see if
anyone else is having problems or has more of a clue than I do.
The only weird thing I'm doing is booting the kernel with qemu's -kernel
argument.
next prev parent reply other threads:[~2025-04-11 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 16:48 [RFC PATCH resend] " Ard Biesheuvel
2025-03-07 23:11 ` [tip: x86/build] " tip-bot2 for Ard Biesheuvel
2025-04-11 19:33 ` Dave Hansen [this message]
2025-04-11 19:52 ` Dave Hansen
2025-04-12 8:48 ` Ingo Molnar
2025-04-18 7:05 ` Ard Biesheuvel
2025-03-11 16:59 ` [RFC PATCH resend] " Vitaly Kuznetsov
2025-03-11 17:14 ` H. Peter Anvin
2025-03-11 17:25 ` Ard Biesheuvel
2025-03-11 17:29 ` H. Peter Anvin
2025-03-11 17:44 ` Ard Biesheuvel
2025-03-12 1:34 ` H. Peter Anvin
2025-03-12 18:57 ` David Laight
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=364ad671-5e5c-47c1-af22-34a7c481f8e3@intel.com \
--to=dave.hansen@intel.com \
--cc=ardb@kernel.org \
--cc=hpa@zytor.com \
--cc=ijc@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®