linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: ERROR: "min_low_pfn" undefined!
Date: Sun, 21 Jun 2020 17:54:37 +0800	[thread overview]
Message-ID: <202006211734.CxzkQlw9%lkp@intel.com> (raw)

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

Hi Jiri,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   64677779e8962c20b580b471790fe42367750599
commit: aebe5fc3b5685e1d9b86cc8314a8e8f3c6f3284e n_hdlc: put init/exit strings directly to prints
date:   4 months ago
config: microblaze-randconfig-c022-20200621 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0

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 >>):

>> ERROR: "min_low_pfn" [drivers/hwtracing/intel_th/intel_th_msu_sink.ko] undefined!
>> ERROR: "min_low_pfn" [drivers/hwtracing/intel_th/intel_th_msu.ko] undefined!
   ERROR: "min_low_pfn" [drivers/usb/core/usbcore.ko] undefined!
>> ERROR: "min_low_pfn" [crypto/essiv.ko] undefined!
>> ERROR: "min_low_pfn" [crypto/tcrypt.ko] undefined!
   ERROR: "min_low_pfn" [crypto/ccm.ko] undefined!
   ERROR: "min_low_pfn" [crypto/gcm.ko] undefined!
   ERROR: "min_low_pfn" [crypto/asymmetric_keys/asym_tpm.ko] undefined!

---
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: 26920 bytes --]

             reply	other threads:[~2020-06-21  9:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21  9:54 kernel test robot [this message]
2020-06-23 15:57 ERROR: "min_low_pfn" undefined! kernel test robot
2020-06-24  3:42 kernel test robot
2020-06-27  3:19 kernel test robot
2020-06-27  6:54 kernel test robot
2020-06-29 21:50 kernel test robot
2020-06-30  2:13 ` David Rientjes
2020-06-30 11:15   ` Mike Rapoport
2020-06-29 22:28 kernel test robot
2020-07-01  0:41 kernel test robot
2020-07-05 19:40 kernel test robot
2020-07-10 10:29 kernel test robot
2020-07-20 16:23 kernel test robot
2020-08-01  2:35 kernel test robot
2020-08-01 20:42 kernel test robot
2020-08-11 10:27 kernel test robot
2020-08-20  2:11 kernel test robot
2020-08-22  3:30 kernel test robot
2020-08-25  2:29 kernel test robot
2020-09-01  5:41 kernel test robot
2020-09-01  5:47 ` Randy Dunlap
2020-09-01 12:05 kernel test robot
2020-09-01 17:59 ` Randy Dunlap

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=202006211734.CxzkQlw9%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.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).