From: Randy Dunlap <rdunlap@infradead.org>
To: Yonghong Song <yhs@meta.com>, kernel test robot <lkp@intel.com>,
Yonghong Song <yhs@fb.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: ERROR: modpost: "iounmap" [drivers/tty/ipwireless/ipwireless.ko] undefined!
Date: Tue, 28 Feb 2023 23:11:57 -0800 [thread overview]
Message-ID: <89ff97ff-310d-579a-63d4-84cf093482d5@infradead.org> (raw)
In-Reply-To: <1f63f410-6bfc-7b59-7a7d-8fca323ada53@meta.com>
On 2/28/23 23:05, Yonghong Song wrote:
>
>
> On 2/28/23 3:22 PM, kernel test robot wrote:
>> Hi Yonghong,
>>
>> First bad commit (maybe != root cause):
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: e492250d5252635b6c97d52eddf2792ec26f1ec1
>> commit: dffbbdc2d9889670c30e07d05fc0dd712e8ad430 libbpf: Add enum64 parsing and new enum64 public API
>> date: 9 months ago
>> config: s390-randconfig-r021-20230227 (https://download.01.org/0day-ci/archive/20230301/202303010701.KWYce0Mt-lkp@intel.com/config )
>> compiler: s390-linux-gcc (GCC) 12.1.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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dffbbdc2d9889670c30e07d05fc0dd712e8ad430
>> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> git fetch --no-tags linus master
>> git checkout dffbbdc2d9889670c30e07d05fc0dd712e8ad430
>> # save the config file
>> mkdir build_dir && cp config build_dir/.config
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=s390 olddefconfig
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash
>
> I don't think the commit 'libbpf: Add enum64 parsing and new enum64 public API' is responsible for the test failure. That commit is purely userspace and should not be the reason for kernel module symbol undefined.
>
CONFIG_HAS_IOMEM is not set. Happens often on ARCH=s390 when CONFIG_PCI is not set.
>>
>> If you fix the issue, kindly add following tag where applicable
>> | Reported-by: kernel test robot <lkp@intel.com>
>> | Link: https://lore.kernel.org/oe-kbuild-all/202303010701.KWYce0Mt-lkp@intel.com/
>>
>> All errors (new ones prefixed by >>, old ones prefixed by <<):
>>
>>>> ERROR: modpost: "iounmap" [drivers/tty/ipwireless/ipwireless.ko] undefined!
>>>> ERROR: modpost: "ioremap" [drivers/tty/ipwireless/ipwireless.ko] undefined!
>> ERROR: modpost: "ioremap" [drivers/net/arcnet/com90xx.ko] undefined!
>> ERROR: modpost: "iounmap" [drivers/net/arcnet/com90xx.ko] undefined!
>>>> ERROR: modpost: "iounmap" [drivers/pcmcia/pcmcia.ko] undefined!
>>>> ERROR: modpost: "ioremap" [drivers/pcmcia/pcmcia.ko] undefined!
>>
--
~Randy
prev parent reply other threads:[~2023-03-01 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 23:22 kernel test robot
2023-03-01 7:05 ` Yonghong Song
2023-03-01 7:11 ` Randy Dunlap [this message]
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=89ff97ff-310d-579a-63d4-84cf093482d5@infradead.org \
--to=rdunlap@infradead.org \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yhs@fb.com \
--cc=yhs@meta.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
all inboxes | Powered by JetHome®