From: Arnd Bergmann <arnd@arndb.de>
To: kernel test robot <lkp@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@linux-xtensa.org>, Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: ERROR: modpost: "__divsi3_table" [lib/lz4/lz4_compress.ko] undefined!
Date: Mon, 6 Dec 2021 12:01:47 +0100 [thread overview]
Message-ID: <CAK8P3a0wboR0evmNGL_VEsNNdLd9x_v8k3APH70t5gfu9D=A6w@mail.gmail.com> (raw)
In-Reply-To: <202112061844.RuSQXzxk-lkp@intel.com>
On Mon, Dec 6, 2021 at 11:30 AM kernel test robot <lkp@intel.com> wrote:
> First bad commit (maybe != root cause):
> commit: 570a82b9c36f76a5959b5e47900629b0d413931d media: i2c: select V4L2_ASYNC where needed
Right, that is clearly unrelated.
> 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: "__divsi3_table" [lib/lz4/lz4_compress.ko] undefined!
lz4 was recently updated, and apparently now does a 32-bit division. I
assume this
is the decompressor, as arch/mips had similar problems.
The possible fixes are:
- disable lz4 compressed kernels on xtensa
- change lz4 to not perform any division
- change the xtensa decompressor to include the divsi3 helper code from the
main kernel, see fbf3bce45821 ("MIPS: boot/compressed/: add __ashldi3 to
target for ZSTD compression")
Arnd
next prev parent reply other threads:[~2021-12-06 11:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 10:30 ERROR: modpost: "__divsi3_table" [lib/lz4/lz4_compress.ko] undefined! kernel test robot
2021-12-06 11:01 ` Arnd Bergmann [this message]
2021-12-24 12:09 ` Max Filippov
-- strict thread matches above, loose matches on Subject: below --
2023-05-13 4:37 kernel test robot
2023-04-18 4:47 kernel test robot
2023-03-11 14:03 kernel test robot
2023-02-17 14:16 kernel test robot
2022-09-30 22:31 kernel test robot
2022-09-20 8:33 kernel test robot
2022-11-24 2:56 ` Randy Dunlap
2022-08-15 2:13 kernel test robot
2022-08-15 8:13 ` Arnd Bergmann
2022-03-13 4:23 kernel test robot
2022-01-13 6:22 kernel test robot
2022-01-12 18:11 kernel test robot
2021-08-04 20:52 kernel test robot
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='CAK8P3a0wboR0evmNGL_VEsNNdLd9x_v8k3APH70t5gfu9D=A6w@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=chris@zankel.net \
--cc=hverkuil@xs4all.nl \
--cc=jcmvbkbc@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=lkp@intel.com \
--cc=mchehab@kernel.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 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).