From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: ERROR: modpost: "__umoddi3" [net/sched/sch_netem.ko] undefined!
Date: Wed, 30 Jun 2021 05:10:27 +0800 [thread overview]
Message-ID: <202106300520.2yGPIgt8-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
tree: https://github.com/0day-ci/linux/commits/UPDATE-20210628-031248/Niclas-Hedam/net-sched-Add-support-for-packet-bursting/20210625-200450
head: b2ff7b8af467b0a1f475753f84970d79848d45eb
commit: b2ff7b8af467b0a1f475753f84970d79848d45eb net: sched: Add support for packet bursting.
date: 2 days ago
config: mips-gpr_defconfig (attached as .config)
compiler: mipsel-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/0day-ci/linux/commit/b2ff7b8af467b0a1f475753f84970d79848d45eb
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review UPDATE-20210628-031248/Niclas-Hedam/net-sched-Add-support-for-packet-bursting/20210625-200450
git checkout b2ff7b8af467b0a1f475753f84970d79848d45eb
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
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: "__umoddi3" [net/sched/sch_netem.ko] undefined!
---
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: 21685 bytes --]
reply other threads:[~2021-06-29 21:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202106300520.2yGPIgt8-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.