Re: [wsa:i2c/for-next 15/29] Inconsistent kallsyms data

[Wolfram Sang <wsa-dev@sang-engineering.com>]

[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]

On Mon, Jun 08, 2020 at 02:53:24PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
> head:   726b03203e45ded63f4479f0b2de7c89d91cf3be
> commit: 786d2af7a5d8b46bc66c20fc886f178c34b936ab [15/29] Merge branch 'i2c/for-5.8' into i2c/for-next
> config: arm-randconfig-r001-20200607 (attached as .config)
> compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project e429cffd4f228f70c1d9df0e5d77c08590dd9766)
> 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
>         # install arm cross compiling tool for clang build
>         # apt-get install binutils-arm-linux-gnueabi
>         git checkout 786d2af7a5d8b46bc66c20fc886f178c34b936ab
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm 
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>, old ones prefixed by <<):
> 
> >> Inconsistent kallsyms data
> Try make KALLSYMS_EXTRA_PASS=1 as a workaround

I have problems parsing this report.

This is a merge commit. Can't it be bisected any further? I couldn't
find anything wrong by visually checking, but I may be missing
something.

Also, does it matter that clang is the compiler here? Does it mean it
does not show up with GCC?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]