linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Mike Snitzer <snitzer@redhat.com>
Subject: Re: ERROR: "min_low_pfn" undefined!
Date: Tue, 1 Sep 2020 10:59:23 -0700	[thread overview]
Message-ID: <0ab89fbf-eb8c-2122-c939-5a7d0db55379@infradead.org> (raw)
In-Reply-To: <202009012005.FyTjySG4%lkp@intel.com>

On 9/1/20 5:05 AM, kernel test robot wrote:
> Hi Ard,
> 
> First bad commit (maybe != root cause):
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   b51594df17d0ce80b9f9f35394a1f42d7ac94472
> commit: be1eb7f78aa8fbe34779c56c266ccd0364604e71 crypto: essiv - create wrapper template for ESSIV generation
> date:   12 months ago
> config: microblaze-randconfig-r003-20200831 (attached as .config)
> compiler: microblaze-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
>         git checkout be1eb7f78aa8fbe34779c56c266ccd0364604e71
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross 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 >>):
> 
>    ERROR: "min_low_pfn" [net/mac80211/mac80211.ko] undefined!
>    ERROR: "min_low_pfn" [drivers/mtd/nand/raw/nand.ko] undefined!
>    ERROR: "min_low_pfn" [drivers/ntb/ntb_transport.ko] undefined!
>>> ERROR: "min_low_pfn" [crypto/essiv.ko] undefined!
>    ERROR: "min_low_pfn" [crypto/tcrypt.ko] undefined!
>    ERROR: "min_low_pfn" [crypto/gcm.ko] undefined!
>    ERROR: "min_low_pfn" [crypto/asymmetric_keys/asym_tpm.ko] undefined!
> 
> ---

Please test this patch:

https://lore.kernel.org/lkml/20200829000110.2408-1-rdunlap@infradead.org/

thanks.
-- 
~Randy


  reply	other threads:[~2020-09-01 17:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 12:05 ERROR: "min_low_pfn" undefined! kernel test robot
2020-09-01 17:59 ` Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-01  5:41 kernel test robot
2020-09-01  5:47 ` Randy Dunlap
2020-08-25  2:29 kernel test robot
2020-08-22  3:30 kernel test robot
2020-08-20  2:11 kernel test robot
2020-08-11 10:27 kernel test robot
2020-08-01 20:42 kernel test robot
2020-08-01  2:35 kernel test robot
2020-07-20 16:23 kernel test robot
2020-07-10 10:29 kernel test robot
2020-07-05 19:40 kernel test robot
2020-07-01  0:41 kernel test robot
2020-06-29 22:28 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-27  6:54 kernel test robot
2020-06-27  3:19 kernel test robot
2020-06-24  3:42 kernel test robot
2020-06-23 15:57 kernel test robot
2020-06-21  9:54 kernel 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=0ab89fbf-eb8c-2122-c939-5a7d0db55379@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=snitzer@redhat.com \
    /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).