From: KernelCI bot <bot@kernelci•org>
To: kernelci-results@groups•io
Cc: regressions@lists•linux.dev, gus@collabora•com,
linux-next@vger•kernel.org
Subject: [REGRESSION] next/master: (build) "byte_rev_table" [lib/zlib_deflate/zlib_deflate.ko] undefined! "by...
Date: Thu, 16 Apr 2026 14:59:04 -0000 [thread overview]
Message-ID: <177635154368.6552.7060101263009785041@8692ffc4d55e> (raw)
Hello,
New build issue found on next/master:
---
"byte_rev_table" [lib/zlib_deflate/zlib_deflate.ko] undefined! "byte_rev_table" [drivers/net/ethernet/spacemit/k1_emac.ko] undefined! "byte_rev_table" [drivers/net/ethernet/stmicro/stmmac/stmmac.ko] undefined! in Module.symvers (/tmp/kci/linux/scripts/Makefile.modpost:147) [logspec:kbuild,kbuild.modpost]
---
- dashboard: https://d.kernelci.org/i/maestro:48f931aecdceb03cad626bb809f8965302b7fc91
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD: 452c3b1ea875276105ac90ba474f72b4cd9b77a2
- tags: next-20260416
Please include the KernelCI tag when submitting a fix:
Reported-by: kernelci.org bot <bot@kernelci•org>
Log excerpt:
=====================================================
ERROR: modpost: "byte_rev_table" [lib/zlib_deflate/zlib_deflate.ko] undefined!
ERROR: modpost: "byte_rev_table" [drivers/net/ethernet/spacemit/k1_emac.ko] undefined!
ERROR: modpost: "byte_rev_table" [drivers/net/ethernet/stmicro/stmmac/stmmac.ko] undefined!
=====================================================
# Builds where the incident occurred:
## defconfig on (riscv):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:69e0eea19b5a968309e4e915
#kernelci issue maestro:48f931aecdceb03cad626bb809f8965302b7fc91
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists•linux.dev
Made with love by the KernelCI team - https://kernelci.org
reply other threads:[~2026-04-16 14:59 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=177635154368.6552.7060101263009785041@8692ffc4d55e \
--to=bot@kernelci$(echo .)org \
--cc=gus@collabora$(echo .)com \
--cc=kernelci-results@groups$(echo .)io \
--cc=kernelci@lists$(echo .)linux.dev \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=regressions@lists$(echo .)linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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