All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Kees Cook <keescook@chromium.org>
Subject: ERROR: modpost: "__divsi3_table" [lib/lz4/lz4_compress.ko] undefined!
Date: Sun, 13 Mar 2022 12:23:55 +0800	[thread overview]
Message-ID: <202203131256.9dyj6eO2-lkp@intel.com> (raw)

Hi Arnd,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   aad611a868d16cdc16a7d4a764cef955293e47e3
commit: 606b102876e3741851dfb09d53f3ee57f650a52c drm: fb_helper: fix CONFIG_FB dependency
date:   5 months ago
config: nios2-randconfig-r014-20220313 (https://download.01.org/0day-ci/archive/20220313/202203131256.9dyj6eO2-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.2.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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=606b102876e3741851dfb09d53f3ee57f650a52c
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 606b102876e3741851dfb09d53f3ee57f650a52c
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nios2 SHELL=/bin/bash

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

>> ERROR: modpost: "__divsi3_table" [lib/lz4/lz4_compress.ko] undefined!

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for SERIAL_CORE_CONSOLE
   Depends on TTY && HAS_IOMEM
   Selected by
   - EARLY_PRINTK

---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

             reply	other threads:[~2022-03-13  4:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13  4:23 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-30  7:27 ERROR: modpost: "__divsi3_table" [lib/lz4/lz4_compress.ko] undefined! kernel test robot
2023-05-13  4:37 kernel test robot
2023-04-18  4:47 kernel test robot
2023-03-11 14:03 kernel test robot
2023-02-17 14:16 kernel test robot
2022-09-30 22:31 kernel test robot
2022-09-20  8:33 kernel test robot
2022-11-24  2:56 ` Randy Dunlap
2022-08-15  2:13 kernel test robot
2022-08-15  8:13 ` Arnd Bergmann
2022-08-15  8:13   ` Arnd Bergmann
2022-01-13  6:22 kernel test robot
2022-01-13  6:22 ` kernel test robot
2022-01-12 18:11 kernel test robot
2022-01-12 18:11 ` kernel test robot
2021-12-06 10:30 kernel test robot
2021-12-06 10:30 ` kernel test robot
2021-12-06 11:01 ` Arnd Bergmann
2021-12-06 11:01   ` Arnd Bergmann
2021-12-24 12:09   ` Max Filippov
2021-12-24 12:09     ` Max Filippov
2021-08-04 20:52 kernel test robot
2021-08-04 20:52 ` 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=202203131256.9dyj6eO2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=kbuild-all@lists.01.org \
    --cc=keescook@chromium.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 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.