From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Borislav Petkov <bp@suse.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Subject: [linux-stable-rc:linux-5.15.y 8690/9817] scripts/link-vmlinux.sh: 123: is_enabled: not found
Date: Tue, 23 Aug 2022 06:43:43 +0800 [thread overview]
Message-ID: <202208230606.C8kP9zQs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
head: a0a7e0b2b8b22901945ea2aef1b65871d718accf
commit: dab72c3c32ccde4f362fff993759b0133448d394 [8690/9817] objtool: Add entry UNRET validation
config: x86_64-buildonly-randconfig-r001-20220822 (https://download.01.org/0day-ci/archive/20220823/202208230606.C8kP9zQs-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=dab72c3c32ccde4f362fff993759b0133448d394
git remote add linux-stable-rc https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git fetch --no-tags linux-stable-rc linux-5.15.y
git checkout dab72c3c32ccde4f362fff993759b0133448d394
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> scripts/link-vmlinux.sh: 123: is_enabled: not found
vmlinux.o: warning: objtool: svm_vcpu_enter_exit()+0x97: call to vmload() leaves .noinstr.text section
vmlinux.o: warning: objtool: fixup_bad_iret()+0x1e: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: in_task_stack()+0xc: call to task_stack_page() leaves .noinstr.text section
vmlinux.o: warning: objtool: in_entry_stack()+0x10: call to cpu_entry_stack() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_setup()+0xa3: call to cpuid_eax() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_read_aux()+0x42: call to {dynamic}() leaves .noinstr.text section
vmlinux.o: warning: objtool: do_machine_check()+0xdf: call to mce_gather_info() leaves .noinstr.text section
ld.lld: error: undefined symbol: fb_set_suspend
>>> referenced by drm_fb_helper.c
>>> gpu/drm/drm_fb_helper.o:(drm_fb_helper_resume_worker) in archive drivers/built-in.a
>>> referenced by drm_fb_helper.c
>>> gpu/drm/drm_fb_helper.o:(drm_fb_helper_set_suspend) in archive drivers/built-in.a
>>> referenced by drm_fb_helper.c
>>> gpu/drm/drm_fb_helper.o:(drm_fb_helper_set_suspend_unlocked) in archive drivers/built-in.a
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-22 22:44 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=202208230606.C8kP9zQs-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@suse.de \
--cc=cascardo@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=peterz@infradead.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