From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [tip:sched/core 18/25] ld.lld: error: vmlinux.a(drivers/scsi/scsi_trace.o):(function scsi_trace_parse_cdb: .text+0xb0): relocation R_RISCV_HI20 out of range: 531330 is not in [-524288, 524287]; references '.L.str.1'
Date: Sat, 17 Oct 2026 11:02:43 +0800 [thread overview]
Message-ID: <202610171107.6ZxJvZXv-lkp@intel.com> (raw)
CC: linux-kernel@vger.kernel.org
CC: x86@kernel.org
TO: Mark Rutland <mark.rutland@arm.com>
CC: Peter Zijlstra <peterz@infradead.org>
CC: Jinjie Ruan <ruanjinjie@huawei.com>
CC: Shrikanth Hegde <sshegde@linux.ibm.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
head: b99b7f60c5b473d374c68b53753153b4aa9e0702
commit: 5b9a28eeed37513778ca6b636253aa8dcf39d55f [18/25] sched: dynamic: Remove HAVE_PREEMPT_DYNAMIC_{CALL,KEY}
config: riscv-randconfig-1001-20261017 (https://download.01.org/0day-ci/archive/20261017/202610171107.6ZxJvZXv-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 6719b9e31d6a93099612c474eec76d9f41d0275a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261017/202610171107.6ZxJvZXv-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/202610171107.6ZxJvZXv-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: vmlinux.a(drivers/scsi/scsi_trace.o):(function scsi_trace_parse_cdb: .text+0xb0): relocation R_RISCV_HI20 out of range: 531330 is not in [-524288, 524287]; references '.L.str.1'
>>> referenced by scsi_trace.c:0 (drivers/scsi/scsi_trace.c:0)
>>> defined in vmlinux.a(drivers/scsi/scsi_trace.o)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-17 3:03 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=202610171107.6ZxJvZXv-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.