linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Cc: kbuild-all@lists.01.org, linux-m68k@lists.linux-m68k.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [m68k:m68k-queue 6/6] WARNING: modpost: vmlinux.o(__ex_table+0x1670): Section mismatch in reference from the (unknown reference) (unknown) to the variable .debug_str:.LASF363
Date: Tue, 16 Jun 2020 00:09:32 +0800	[thread overview]
Message-ID: <202006160029.SKwoK80t%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git m68k-queue
head:   6b12625aca1ff016cef6e39975e6a59f23014b91
commit: 6b12625aca1ff016cef6e39975e6a59f23014b91 [6/6] fat: Use correct logical sector size for Atari GEMDOS FAT
config: riscv-randconfig-r013-20200615 (attached as .config)
compiler: riscv32-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 6b12625aca1ff016cef6e39975e6a59f23014b91
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>, old ones prefixed by <<):

<< WARNING: modpost: vmlinux.o(__ex_table+0x1670): Section mismatch in reference from the (unknown reference) (unknown) to the variable .debug_str:.LASF366
>> WARNING: modpost: vmlinux.o(__ex_table+0x1670): Section mismatch in reference from the (unknown reference) (unknown) to the variable .debug_str:.LASF363
FATAL: modpost: The relocation at __ex_table+0x1670 references
section ".debug_str" which is not executable, IOW
it is not possible for the kernel to fault
at that address.  Something is seriously wrong
and should be fixed.

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

                 reply	other threads:[~2020-06-15 16:28 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=202006160029.SKwoK80t%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=geert@linux-m68k.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=schmitz@biophys.uni-duesseldorf.de \
    /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).