tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master head: 593ef1658ecf61d3619885bdbbcfffa3d1417891 commit: 249be5f071ba3f757259f3686b5983ef1e1bfa66 [13289/14048] lib: add fast path for find_next_*_bit() config: xtensa-randconfig-r031-20210420 (attached as .config) compiler: xtensa-linux-gcc (GCC) 9.3.0 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/next/linux-next.git/commit/?id=249be5f071ba3f757259f3686b5983ef1e1bfa66 git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git git fetch --no-tags linux-next master git checkout 249be5f071ba3f757259f3686b5983ef1e1bfa66 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=xtensa If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot All warnings (new ones prefixed by >>, old ones prefixed by <<): >> WARNING: modpost: vmlinux.o(.text.unlikely+0x530): Section mismatch in reference from the function jent_panic() to the variable .init.data:initcall_level_names The function jent_panic() references the variable __initdata initcall_level_names. This is often because jent_panic lacks a __initdata annotation or the annotation of initcall_level_names is wrong. --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org