From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============8113647156568971385=="
MIME-Version: 1.0
From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [wsa:i2c/for-next 15/29] Inconsistent kallsyms data
Date: Tue, 09 Jun 2020 22:44:37 +0800
Message-ID: <20200609144437.GA19950@intel.com>
In-Reply-To: <06988020-878b-54da-2b00-afe746f94c76@intel.com>
List-Id: <oe-kbuild-all.lists.linux.dev>

--===============8113647156568971385==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

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=3D1 build):
> > >          wget https://raw.githubusercontent.com/intel/lkp-tests/maste=
r/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=3D$HOME/0day COMPILER=3Dclang make.cro=
ss ARCH=3Darm
> > > =

> > > 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=3D1 as a workaround
> > I have problems parsing this report.
> > =

> > This is a merge commit. Can't it be bisected any further?
> +Rong,
> =

> =C2=A0could 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
--===============8113647156568971385==--