From: kernel test robot <lkp@intel.com>
To: Feng Tang <feng.tang@intel.com>
Cc: kbuild-all@lists.01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [hnaz-linux-mm:master 286/421] Inconsistent kallsyms data
Date: Thu, 1 Oct 2020 12:55:08 +0800 [thread overview]
Message-ID: <202010011203.AKw3Hkqw-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
tree: https://github.com/hnaz/linux-mm master
head: 2932a9e66c580f3c8d95ec27716d437198fb4c94
commit: 17e9cbdd5b55c376f45b8a19f6057ba0b91f1178 [286/421] ./Makefile: add debug option to enable function aligned on 32 bytes
config: powerpc-allmodconfig (attached as .config)
compiler: powerpc64-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://github.com/hnaz/linux-mm/commit/17e9cbdd5b55c376f45b8a19f6057ba0b91f1178
git remote add hnaz-linux-mm https://github.com/hnaz/linux-mm
git fetch --no-tags hnaz-linux-mm master
git checkout 17e9cbdd5b55c376f45b8a19f6057ba0b91f1178
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
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 >>):
>> 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@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 69612 bytes --]
next reply other threads:[~2020-10-01 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 4:55 kernel test robot [this message]
2020-10-09 6:59 ` [hnaz-linux-mm:master 286/421] Inconsistent kallsyms data Feng Tang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202010011203.AKw3Hkqw-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).