From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: ld.lld: error: undefined symbol: xe_configfs_get_ctx_restore_mid_bb
Date: Fri, 13 Feb 2026 17:10:01 +0800 [thread overview]
Message-ID: <202602131722.ZXfVklUT-lkp@intel.com> (raw)
Hi Lucas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: cee73b1e840c154f64ace682cb477c1ae2e29cc4
commit: 7a4756b2fd0431f109b07b904a7442f00838abf9 drm/xe/lrc: Allow to add user commands mid context switch
date: 5 months ago
config: x86_64-randconfig-r052-20260212 (https://download.01.org/0day-ci/archive/20260213/202602131722.ZXfVklUT-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260213/202602131722.ZXfVklUT-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/202602131722.ZXfVklUT-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: xe_configfs_get_ctx_restore_mid_bb
>>> referenced by xe_lrc.c:87 (drivers/gpu/drm/xe/xe_lrc.c:87)
>>> vmlinux.o:(xe_lrc_create)
>>> referenced by xe_lrc.c:1151 (drivers/gpu/drm/xe/xe_lrc.c:1151)
>>> vmlinux.o:(setup_configfs_mid_ctx_restore_bb)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-02-13 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 9:10 kernel test robot [this message]
2026-05-23 18:37 kernel test robot
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=202602131722.ZXfVklUT-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.vivi@intel.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
all inboxes | Powered by JetHome®