From: kernel test robot <lkp@intel.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Alexandre Courbot <acourbot@nvidia.com>,
Eliot Courtney <ecourtney@nvidia.com>
Subject: vmlinux.o: error: objtool: _RNvMs_NtNtCs6PUMngfe6Jo_9nova_core3gsp4bootNtB6_3Gsp4boot+0xd90: can't find jump dest instruction at .text._RNvMs_NtNtCs6PUMngfe6Jo_9nova_core3gsp4bootNtB6_3Gsp4boot+0x1df6
Date: Thu, 13 Aug 2026 16:28:17 +0800 [thread overview]
Message-ID: <202608131616.Go6giy15-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3d6d817622b0a9721e3cc404df3469171582be13
commit: f66287cf155e47b604118ee1e7731ff634d8dbe9 gpu: nova-core: Hopper/Blackwell: larger WPR2 (GSP) heap
date: 2 months ago
config: x86_64-randconfig-011-20260813 (https://download.01.org/0day-ci/archive/20260813/202608131616.Go6giy15-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260813/202608131616.Go6giy15-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
| Fixes: f66287cf155e ("gpu: nova-core: Hopper/Blackwell: larger WPR2 (GSP) heap")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608131616.Go6giy15-lkp@intel.com/
All errors (new ones prefixed by >>):
>> vmlinux.o: error: objtool: _RNvMs_NtNtCs6PUMngfe6Jo_9nova_core3gsp4bootNtB6_3Gsp4boot+0xd90: can't find jump dest instruction at .text._RNvMs_NtNtCs6PUMngfe6Jo_9nova_core3gsp4bootNtB6_3Gsp4boot+0x1df6
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-13 8:29 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=202608131616.Go6giy15-lkp@intel.com \
--to=lkp@intel.com \
--cc=acourbot@nvidia.com \
--cc=ecourtney@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox