From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/boot] BUILD REGRESSION 893930143440eb5e3ea8f69cb51ab2e61e15c4e1
Date: Wed, 08 Jan 2025 09:06:11 +0800 [thread overview]
Message-ID: <202501080904.dxMfXzKu-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/boot
branch HEAD: 893930143440eb5e3ea8f69cb51ab2e61e15c4e1 x86/sev: Don't hang but terminate on failure to remap SVSM CA
Error/Warning (recently discovered and may have been fixed):
https://lore.kernel.org/oe-kbuild-all/202501072244.zZrx9864-lkp@intel.com
Absolute reference to symbol '.data' not permitted in .head.text
Error/Warning ids grouped by kconfigs:
recent_errors
`-- x86_64-randconfig-103-20250107
`-- Absolute-reference-to-symbol-.data-not-permitted-in-.head.text
elapsed time: 737m
configs tested: 19
configs skipped: 135
tested configs:
i386 allmodconfig gcc-12
i386 allnoconfig gcc-12
i386 allyesconfig gcc-12
i386 buildonly-randconfig-001-20250107 clang-19
i386 buildonly-randconfig-002-20250107 clang-19
i386 buildonly-randconfig-003-20250107 clang-19
i386 buildonly-randconfig-004-20250107 gcc-12
i386 buildonly-randconfig-005-20250107 gcc-12
i386 buildonly-randconfig-006-20250107 clang-19
i386 defconfig clang-19
x86_64 allnoconfig clang-19
x86_64 allyesconfig clang-19
x86_64 buildonly-randconfig-001-20250107 clang-19
x86_64 buildonly-randconfig-002-20250107 gcc-12
x86_64 buildonly-randconfig-003-20250107 clang-19
x86_64 buildonly-randconfig-004-20250107 gcc-12
x86_64 buildonly-randconfig-005-20250107 clang-19
x86_64 buildonly-randconfig-006-20250107 clang-19
x86_64 defconfig gcc-11
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-08 1:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202501080904.dxMfXzKu-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.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