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

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

[kernel test robot]

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

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

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 37040 bytes --]

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

[Wolfram Sang]

[-- 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 --]

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

[Li Zhijian]

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



On 6/8/20 4:24 PM, Wolfram Sang wrote:
> 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?
+Rong,

  could you help to answer this question

> 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?
i checked the gcc result, its' good.

Please note that generally 0Day/LKP will build a lots of combinations of 
different compilers(gcc-7, gcc-8, gcc-9, clang etc) and different kconfigs
Each combination will generate a individual report if something wrong 
are detected.


Thanks

>
>
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org

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

[Philip Li]

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

On Tue, Jun 09, 2020 at 06:12:14PM +0800, Li Zhijian wrote:
> 
> 
> On 6/8/20 4:24 PM, Wolfram Sang wrote:
> > 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?
> +Rong,
> 
>  could you help to answer this question
> 
> > 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?
> i checked the gcc result, its' good.
Cc clang list, to help share some hints for this.

> 
> Please note that generally 0Day/LKP will build a lots of combinations of
> different compilers(gcc-7, gcc-8, gcc-9, clang etc) and different kconfigs
> Each combination will generate a individual report if something wrong are
> detected.
> 
> 
> Thanks
> 
> > 
> > 
> > _______________________________________________
> > kbuild-all mailing list -- kbuild-all(a)lists.01.org
> > To unsubscribe send an email to kbuild-all-leave(a)lists.01.org
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org

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

[Nick Desaulniers]

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

On Tue, Jun 9, 2020 at 7:45 AM Philip Li <philip.li@intel.com> wrote:
>
> On Tue, Jun 09, 2020 at 06:12:14PM +0800, Li Zhijian wrote:
> >
> >
> > On 6/8/20 4:24 PM, Wolfram Sang wrote:
> > > 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?
> > +Rong,
> >
> >  could you help to answer this question
> >
> > > 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?
> > i checked the gcc result, its' good.
> Cc clang list, to help share some hints for this.

Thanks for the report. Can you please provide a link to the original
report for more context?

>
> >
> > Please note that generally 0Day/LKP will build a lots of combinations of
> > different compilers(gcc-7, gcc-8, gcc-9, clang etc) and different kconfigs
> > Each combination will generate a individual report if something wrong are
> > detected.
-- 
Thanks,
~Nick Desaulniers

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

[Rong Chen]

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



On 6/10/20 2:06 AM, Nick Desaulniers wrote:
> On Tue, Jun 9, 2020 at 7:45 AM Philip Li <philip.li@intel.com> wrote:
>> On Tue, Jun 09, 2020 at 06:12:14PM +0800, Li Zhijian wrote:
>>>
>>> On 6/8/20 4:24 PM, Wolfram Sang wrote:
>>>> 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?
>>> +Rong,
>>>
>>>   could you help to answer this question
>>>
>>>> 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?
>>> i checked the gcc result, its' good.
>> Cc clang list, to help share some hints for this.
> Thanks for the report. Can you please provide a link to the original
> report for more context?
>

Hi Nick,

The original report is 
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org/thread/TRPRDXHL2OD5CNPSZQE3TPTRWW6E7YC5/

Best Regards,
Rong Chen

[-- Attachment #2: i2c_for-next15_29Inconsistentkallsymsdata.eml --]
[-- Type: message/rfc822, Size: 52 bytes --]



WzxlbWFpbC5tZXNzYWdlLk1lc3NhZ2UgaW5zdGFuY2UgYXQgMHg3ZmM5MWE1ODAxZTA+XQ==

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

[Wolfram Sang]

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


> > Also, does it matter that clang is the compiler here? Does it mean it
> > does not show up with GCC?
> i checked the gcc result, its' good.

Thank you for the heads up. Then, I'll leave my tree as is and leave it
to you and the clang folks for now. OK?


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

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

[Rong Chen]

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



On 6/9/20 6:12 PM, Li Zhijian wrote:
>
>
> On 6/8/20 4:24 PM, Wolfram Sang wrote:
>> 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?
> +Rong,
>
>  could you help to answer this question

The final first bad commit is the merge commit, both the two parent 
commits are good.

Best Regards,
Rong Chen