From: kernel test robot <lkp@intel.com>
To: Danielle Ratson <danieller@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Petr Machata <petrm@nvidia.com>
Subject: [linux-next:master 8719/10451] ld.lld: error: section .pci_fixup virtual address range overlaps with __bug_table
Date: Fri, 5 Jul 2024 14:09:37 +0800 [thread overview]
Message-ID: <202407051359.IdUPkWid-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 0b58e108042b0ed28a71cd7edf5175999955b233
commit: a39c84d796254e6b1662ca0c46dbc313379e9291 [8719/10451] ethtool: cmis_cdb: Add a layer for supporting CDB commands
config: riscv-randconfig-001-20240704 (https://download.01.org/0day-ci/archive/20240705/202407051359.IdUPkWid-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project a0c6b8aef853eedaa0980f07c0a502a5a8a9740e)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240705/202407051359.IdUPkWid-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407051359.IdUPkWid-lkp@intel.com/
Note: the linux-next/master HEAD 0b58e108042b0ed28a71cd7edf5175999955b233 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
>> ld.lld: error: section .pci_fixup virtual address range overlaps with __bug_table
>>> .pci_fixup range is [0xFFFFFFFF826C79D8, 0xFFFFFFFF826CB9DF]
>>> __bug_table range is [0xFFFFFFFF826CA788, 0xFFFFFFFF8270CE6B]
--
>> ld.lld: error: section __bug_table virtual address range overlaps with __ksymtab
>>> __bug_table range is [0xFFFFFFFF826CA788, 0xFFFFFFFF8270CE6B]
>>> __ksymtab range is [0xFFFFFFFF826CB9E0, 0xFFFFFFFF826EE86F]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-05 6: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=202407051359.IdUPkWid-lkp@intel.com \
--to=lkp@intel.com \
--cc=danieller@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=petrm@nvidia.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