From: kernel test robot <oliver.sang@intel.com>
To: Khalid Ali <khaliidcaliy@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <tglx@linutronix.de>,
<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<x86@kernel.org>, <hpa@zytor.com>,
Khalid Ali <khaliidcaliy@gmail.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH v4] x86/boot: Don't return encryption mask from __startup_64()
Date: Wed, 25 Jun 2025 14:40:07 +0800 [thread overview]
Message-ID: <202506251439.913b4c32-lkp@intel.com> (raw)
In-Reply-To: <20250619073652.719-1-khaliidcaliy@gmail.com>
Hello,
kernel test robot noticed "BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)" on:
commit: ceefc6a6846712aaeee61b8dfa97d5c33313d063 ("[PATCH v4] x86/boot: Don't return encryption mask from __startup_64()")
url: https://github.com/intel-lab-lkp/linux/commits/Khalid-Ali/x86-boot-Don-t-return-encryption-mask-from-__startup_64/20250619-153838
base: https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git 6a7c3c2606105a41dde81002c0037420bc1ddf00
patch link: https://lore.kernel.org/all/20250619073652.719-1-khaliidcaliy@gmail.com/
patch subject: [PATCH v4] x86/boot: Don't return encryption mask from __startup_64()
in testcase: boot
config: x86_64-kexec
compiler: clang-20
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+--------------------------------------------------------------------------------------+------------+------------+
| | 6a7c3c2606 | ceefc6a684 |
+--------------------------------------------------------------------------------------+------------+------------+
| boot_successes | 6 | 0 |
| boot_failures | 0 | 6 |
| BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#) | 0 | 6 |
+--------------------------------------------------------------------------------------+------------+------------+
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202506251439.913b4c32-lkp@intel.com
trampoline_32bit: 0x0000000000000000
Decompressing Linux... Parsing ELF... done.
Booting the kernel (entry_offset: 0x0000000001161e30).
convert early boot stage from reboot-without-warning to failed
BUG: kernel failed in early-boot stage, last printk: Booting the kernel (entry_offset: 0x0000000001161e30).
Linux version 6.15.0-rc7-00359-gceefc6a68467 #1
Command line: ip=::::vm-meta-270::dhcp root=/dev/ram0 RESULT_ROOT=/result/boot/1/vm-snb/debian-11.1-i386-20220923.cgz/x86_64-kexec/clang-20/ceefc6a6846712aaeee61b8dfa97d5c33313d063/0 BOOT_IMAGE=/pkg/linux/x86_64-kexec/clang-20/ceefc6a6846712aaeee61b8dfa97d5c33313d063/vmlinuz-6.15.0-rc7-00359-gceefc6a68467 branch=linux-devel/devel-hourly-20250619-233935 job=/lkp/jobs/scheduled/vm-meta-270/boot-1-debian-11.1-i386-20220923.cgz-ceefc6a68467-20250621-121357-1bgjd25-0.yaml user=lkp ARCH=x86_64 kconfig=x86_64-kexec commit=ceefc6a6846712aaeee61b8dfa97d5c33313d063 intremap=posted_msi vmalloc=256M initramfs_async=0 page_owner=on carrier_timeout=60 rcupdate.rcu_self_test=0 max_uptime=600 LKP_SERVER=internal-lkp-server selinux=0 debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 net.ifnames=0 printk.devkmsg=on panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 drbd.minor_count=8 systemd.log_level=err ignore_loglevel console=tty0 earlyprintk=ttyS0,115200 console=ttyS0,115200 vga=normal rw rcuperf.shutdown=0 rcuscale.shutdown=0 refscale.shutdown=0 watchdog_thresh=240 audit=0 kunit.enable=0 ia32_emulation=on riscv_isa_fallback=1
Kboot worker: lkp-worker51
Elapsed time: 60
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250625/202506251439.913b4c32-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-25 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 7:36 Khalid Ali
2025-06-23 11:26 ` Huang, Kai
2025-06-25 6:40 ` kernel test robot [this message]
2025-06-25 10:55 ` Huang, Kai
2025-06-25 12:34 ` Khalid Ali
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=202506251439.913b4c32-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=khaliidcaliy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tglx@linutronix.de \
--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®