From: kernel test robot <lkp@intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Alexey Gladkov <legion@kernel.org>,
Nicolas Schier <nsc@kernel.org>
Subject: xtensa-linux-objcopy: st2a95ta: warning: allocated section `.DebugInterruptVector.text' not in segment
Date: Fri, 30 Jan 2026 22:47:59 +0800 [thread overview]
Message-ID: <202601302238.EohgQKKM-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4d310797262f0ddf129e76c2aad2b950adaf1fda
commit: 3e86e4d74c0490e5fc5a7f8de8f29e7579c9ffe5 kbuild: keep .modinfo section in vmlinux.unstripped
date: 4 months ago
config: xtensa-randconfig-r073-20260130 (https://download.01.org/0day-ci/archive/20260130/202601302238.EohgQKKM-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 15.2.0
smatch version: v0.5.0-8994-gd50c5a4c
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260130/202601302238.EohgQKKM-lkp@intel.com/reproduce)
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 <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601302238.EohgQKKM-lkp@intel.com/
All warnings (new ones prefixed by >>):
xtensa-linux-objcopy: vmlinux: section `.WindowVectors.text' can't be allocated in segment 1
LOAD: .data .init.text .init.data .init.rodata .data..percpu .dummy .WindowVectors.text
xtensa-linux-objcopy: vmlinux: section `.DebugInterruptVector.text' can't be allocated in segment 3
LOAD: .WindowVectors.text .DebugInterruptVector.text
>> xtensa-linux-objcopy: st2a95ta: warning: allocated section `.DebugInterruptVector.text' not in segment
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-30 14:48 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=202601302238.EohgQKKM-lkp@intel.com \
--to=lkp@intel.com \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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®