From: kernel test robot <[email protected]>
To: "Jason A. Donenfeld" <[email protected]>
Cc: [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected]
Subject: [ammarfaizi2-block:crng/random/master 29/29] WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in reference from the variable .L0 to the variable .debug_str:.LASF1747
Date: Mon, 9 May 2022 16:33:29 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block crng/random/master
head: 26bcbb981eb1ab60612d6cee1bb1b5f444a23ef2
commit: 26bcbb981eb1ab60612d6cee1bb1b5f444a23ef2 [29/29] random: use symbolic constants for crng_init states
config: riscv-randconfig-r042-20220509 (https://download.01.org/0day-ci/archive/20220509/[email protected]/config)
compiler: riscv32-linux-gcc (GCC) 11.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/ammarfaizi2/linux-block/commit/26bcbb981eb1ab60612d6cee1bb1b5f444a23ef2
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block crng/random/master
git checkout 26bcbb981eb1ab60612d6cee1bb1b5f444a23ef2
# save the config file
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in reference from the variable .L0 to the variable .debug_str:.LASF1747
FATAL: modpost: extable_entry size hasn't been discovered!
Note: the below error/warnings can be found in parent commit:
<< WARNING: modpost: vmlinux.o(.text+0xa76b86): Section mismatch in reference from the function rtc_update_irq() to the variable .init.text:.L0
<< WARNING: modpost: vmlinux.o(.text+0xbacbf2): Section mismatch in reference from the function comedi_buf_map_get() to the variable .init.text:.L0
<< WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in reference from the variable .L0 to the variable .debug_str:.LASF1744
<< WARNING: modpost: vmlinux.o(.text+0xae24ec): Section mismatch in reference from the function ir_raw_get_allowed_protocols() to the variable .init.text:.L0
<< WARNING: modpost: vmlinux.o(.text+0xae2b2e): Section mismatch in reference from the function ir_raw_event_prepare() to the variable .init.text:.L0
<< WARNING: modpost: vmlinux.o(.text+0xae2c8c): Section mismatch in reference from the function ir_raw_event_free() to the variable .init.text:.L0
<< WARNING: modpost: vmlinux.o(.text+0xae2cb0): Section mismatch in reference from the function ir_raw_event_unregister() to the variable .init.text:.L0
<< WARNING: modpost: vmlinux.o(.text+0xb1f67e): Section mismatch in reference from the function thermal_zone_device_enable() to the variable .init.text:.L0
<< WARNING: modpost: vmlinux.o(.text+0xb1f688): Section mismatch in reference from the function thermal_zone_device_disable() to the variable .init.text:.L0
<< WARNING: modpost: vmlinux.o(.text+0xb201d8): Section mismatch in reference from the function thermal_of_cooling_device_register() to the variable .init.text:.L0
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-05-09 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 8:33 kernel test robot [this message]
2022-05-09 12:46 ` [ammarfaizi2-block:crng/random/master 29/29] WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in reference from the variable .L0 to the variable .debug_str:.LASF1747 Philip Li
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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