Re: ERROR: start_text address is c000000000000500, should be c000000000000100

From: Randy Dunlap
Date: Tue Apr 26 2022 - 21:11:24 EST


Hi bot--

On 4/24/22 02:36, kernel test robot wrote:
> Hi Randy,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 22da5264abf497a10a4ed629f07f4ba28a7ed5eb
> commit: 47c258d71ebfc832a760a1dc6540cf3c33968023 powerpc/head_check: use stdout for error messages
> date: 8 months ago
> config: powerpc64-randconfig-m031-20220424 (https://download.01.org/0day-ci/archive/20220424/202204241730.Ly1j4bUG-lkp@xxxxxxxxx/config)
> compiler: powerpc64-linux-gcc (GCC) 11.2.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/torvalds/linux.git/commit/?id=47c258d71ebfc832a760a1dc6540cf3c33968023
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 47c258d71ebfc832a760a1dc6540cf3c33968023
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross W=1 O=build_dir ARCH=powerpc SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@xxxxxxxxx>
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: start_text address is c000000000000500, should be c000000000000100
>>> ERROR: try to enable LD_HEAD_STUB_CATCH config option
>>> ERROR: see comments in arch/powerpc/tools/head_check.sh

# CONFIG_MODULES is not set

For this one, I didn't enable CONFIG_EXPERT and LD_HEAD_STUB_CATCH.
I just converted everything possible to be loadable modules
and that resolved the problem.

Michael- do you want any addition(s) to the head_check.sh error
messages, such as:

(a) enable CONFIG_EXPERT and LD_HEAD_STUB_CATCH
(the latter requires the former)
or (b) if CONFIG_MODULES is not enabled, enable it
and change drivers to loadable modules until the ERROR
is resolved.

--
~Randy