From: kernel test robot <lkp@intel.com>
To: Michal Simek <monstr@monstr.eu>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: undefined reference to `start_isolate_page_range'
Date: Sat, 21 Nov 2020 09:26:11 +0800 [thread overview]
Message-ID: <202011210906.WVDfrAtS-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1732 bytes --]
Hi Michal,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4ccf7a01e805f04defd423fb410f47a13af76399
commit: 2602276d3d3811b1a48c48113042cd75fcbfc27d microblaze: Wire CMA allocator
date: 10 months ago
config: microblaze-randconfig-s031-20201121 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-134-gb59dbdaf-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2602276d3d3811b1a48c48113042cd75fcbfc27d
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 2602276d3d3811b1a48c48113042cd75fcbfc27d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=microblaze
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 >>):
microblaze-linux-ld: mm/page_alloc.o: in function `alloc_contig_range':
>> (.text+0xa1fc): undefined reference to `start_isolate_page_range'
>> microblaze-linux-ld: (.text+0xa40c): undefined reference to `test_pages_isolated'
>> microblaze-linux-ld: (.text+0xa47c): undefined reference to `undo_isolate_page_range'
---
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: 25673 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: undefined reference to `start_isolate_page_range'
Date: Sat, 21 Nov 2020 09:26:11 +0800 [thread overview]
Message-ID: <202011210906.WVDfrAtS-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]
Hi Michal,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4ccf7a01e805f04defd423fb410f47a13af76399
commit: 2602276d3d3811b1a48c48113042cd75fcbfc27d microblaze: Wire CMA allocator
date: 10 months ago
config: microblaze-randconfig-s031-20201121 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-134-gb59dbdaf-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2602276d3d3811b1a48c48113042cd75fcbfc27d
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 2602276d3d3811b1a48c48113042cd75fcbfc27d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=microblaze
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 >>):
microblaze-linux-ld: mm/page_alloc.o: in function `alloc_contig_range':
>> (.text+0xa1fc): undefined reference to `start_isolate_page_range'
>> microblaze-linux-ld: (.text+0xa40c): undefined reference to `test_pages_isolated'
>> microblaze-linux-ld: (.text+0xa47c): undefined reference to `undo_isolate_page_range'
---
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: 25673 bytes --]
next reply other threads:[~2020-11-21 1:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 1:26 kernel test robot [this message]
2020-11-21 1:26 ` undefined reference to `start_isolate_page_range' kernel test robot
2020-11-23 1:13 ` Randy Dunlap
2020-11-23 1:13 ` Randy Dunlap
2020-11-23 15:21 ` Michal Simek
2020-11-23 15:21 ` Michal Simek
-- strict thread matches above, loose matches on Subject: below --
2020-11-14 23:47 kernel test robot
2020-11-14 23:47 ` kernel test robot
2020-10-11 7:53 kernel test robot
2020-10-11 7:53 ` kernel test robot
2020-09-15 8:39 kernel test robot
2020-09-06 16:17 kernel test robot
2020-09-06 16:17 ` kernel test robot
2020-09-07 22:40 ` Randy Dunlap
2020-09-07 22:40 ` Randy Dunlap
2020-09-07 22:45 ` Philip Li
2020-08-17 22:50 kernel test robot
2020-08-17 22:50 ` kernel test robot
2020-07-27 4:49 kernel test robot
2020-07-27 4:49 ` kernel test robot
2020-07-07 13:57 kernel test robot
2020-07-07 13:57 ` kernel test robot
2020-06-24 11:14 kernel test robot
2020-06-24 11:14 ` kernel test robot
2020-06-12 7:51 kernel test robot
2020-06-12 7:51 ` kernel test robot
2020-05-25 1:24 kbuild test robot
2020-05-25 1:24 ` kbuild test robot
2020-05-16 20:58 kbuild test robot
2020-05-16 20:58 ` kbuild test robot
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=202011210906.WVDfrAtS-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.