From: kernel test robot <lkp@intel.com>
To: Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-kernel@vger.kernel.org,
Trilok Soni <quic_tsoni@quicinc.com>,
Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Elliot Berman <quic_eberman@quicinc.com>,
Guru Das Srinagesh <quic_gurus@quicinc.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Melody Olvera <quic_molvera@quicinc.com>,
Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>
Subject: Re: [PATCH v5 2/2] remoteproc: qcom: Add remoteproc tracing
Date: Tue, 13 Jun 2023 14:19:03 +0800 [thread overview]
Message-ID: <202306131424.QEYiIiQA-lkp@intel.com> (raw)
In-Reply-To: <12b533c73b8c6b039e90f20afef1c8dcd30b80de.1686606835.git.quic_gokukris@quicinc.com>
Hi Gokul,
kernel test robot noticed the following build errors:
[auto build test ERROR on 1ca04f21b204e99dd704146231adfb79ea2fb366]
url: https://github.com/intel-lab-lkp/linux/commits/Gokul-krishna-Krishnakumar/remoteproc-Introduce-traces-for-remoteproc-events/20230613-060527
base: 1ca04f21b204e99dd704146231adfb79ea2fb366
patch link: https://lore.kernel.org/r/12b533c73b8c6b039e90f20afef1c8dcd30b80de.1686606835.git.quic_gokukris%40quicinc.com
patch subject: [PATCH v5 2/2] remoteproc: qcom: Add remoteproc tracing
config: hexagon-randconfig-r041-20230612 (https://download.01.org/0day-ci/archive/20230613/202306131424.QEYiIiQA-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 1ca04f21b204e99dd704146231adfb79ea2fb366
b4 shazam https://lore.kernel.org/r/12b533c73b8c6b039e90f20afef1c8dcd30b80de.1686606835.git.quic_gokukris@quicinc.com
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=hexagon olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash
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/202306131424.QEYiIiQA-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: __tracepoint_rproc_start_event
>>> referenced by jump_label.h:260 (include/linux/jump_label.h:260)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_boot) in archive vmlinux.a
>>> referenced by jump_label.h:260 (include/linux/jump_label.h:260)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_boot) in archive vmlinux.a
>>> referenced by jump_label.h:260 (include/linux/jump_label.h:260)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_boot) in archive vmlinux.a
>>> referenced 1 more times
--
>> ld.lld: error: undefined symbol: __traceiter_rproc_start_event
>>> referenced by remoteproc_tracepoints.h:63 (include/trace/events/remoteproc_tracepoints.h:63)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_boot) in archive vmlinux.a
>>> referenced by remoteproc_tracepoints.h:63 (include/trace/events/remoteproc_tracepoints.h:63)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_boot) in archive vmlinux.a
>>> referenced by remoteproc_tracepoints.h:63 (include/trace/events/remoteproc_tracepoints.h:63)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_boot) in archive vmlinux.a
>>> referenced 1 more times
--
>> ld.lld: error: undefined symbol: __tracepoint_rproc_load_segment_event
>>> referenced by remoteproc_internal.h:178 (drivers/remoteproc/remoteproc_internal.h:178)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_start) in archive vmlinux.a
>>> referenced by remoteproc_internal.h:178 (drivers/remoteproc/remoteproc_internal.h:178)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_start) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: __traceiter_rproc_load_segment_event
>>> referenced by remoteproc_tracepoints.h:17 (include/trace/events/remoteproc_tracepoints.h:17)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_start) in archive vmlinux.a
>>> referenced by remoteproc_tracepoints.h:17 (include/trace/events/remoteproc_tracepoints.h:17)
>>> drivers/remoteproc/remoteproc_core.o:(rproc_start) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: __tracepoint_rproc_stop_event
>>> referenced by jump_label.h:260 (include/linux/jump_label.h:260)
>>> drivers/remoteproc/remoteproc_core.o:(trace_rproc_stop_event) in archive vmlinux.a
>>> referenced by jump_label.h:260 (include/linux/jump_label.h:260)
>>> drivers/remoteproc/remoteproc_core.o:(trace_rproc_stop_event) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: __traceiter_rproc_stop_event
>>> referenced by remoteproc_tracepoints.h:82 (include/trace/events/remoteproc_tracepoints.h:82)
>>> drivers/remoteproc/remoteproc_core.o:(trace_rproc_stop_event) in archive vmlinux.a
>>> referenced by remoteproc_tracepoints.h:82 (include/trace/events/remoteproc_tracepoints.h:82)
>>> drivers/remoteproc/remoteproc_core.o:(trace_rproc_stop_event) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-13 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 22:03 [PATCH v5 0/2] Patches for introducing traces in remoteproc Gokul krishna Krishnakumar
2023-06-12 22:03 ` [PATCH v5 1/2] remoteproc: Introduce traces for remoteproc events Gokul krishna Krishnakumar
2023-06-12 22:03 ` [PATCH v5 2/2] remoteproc: qcom: Add remoteproc tracing Gokul krishna Krishnakumar
2023-06-13 6:08 ` kernel test robot
2023-06-13 6:19 ` kernel test robot [this message]
2023-06-13 7:42 ` kernel test robot
2023-06-13 15:28 ` Steven Rostedt
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=202306131424.QEYiIiQA-lkp@intel.com \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_eberman@quicinc.com \
--cc=quic_gokukris@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=quic_molvera@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=quic_tsoni@quicinc.com \
/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;
as well as URLs for NNTP newsgroup(s).