From: Randy Dunlap <rdunlap@infradead.org>
To: Srishti Sharma <srishtishar@gmail.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: Unknown symbols in module (iio)
Date: Sat, 17 Mar 2018 13:42:24 -0700 [thread overview]
Message-ID: <a1ceed29-158a-5ba8-6b05-cddd043baef8@infradead.org> (raw)
In-Reply-To: <CAB3L5ow-gf0Z7NCRW1V0v+spRF553zx=J_pwc5m5YXxW4S27Lg@mail.gmail.com>
[adding linux-iio mailing list]
Hi,
It's always a good idea to include the kernel version in a problem report.
On 03/05/2018 03:17 AM, Srishti Sharma wrote:
> Hello,
> I was trying to work with the iio dummy driver, and when I try to load
> the iio_dummy_evgen.ko module I am getting unknown symbols found in
> module error on running modprobe.
>
> These variables are unknown
> iio_bus_type >>> in industrialio-core
> irq_sim_init >>> in iio_dummy_evgen
> irq_sim_fini >>> same
> irq_sim_fire >>> same
> irq_sim_fini >>> [duplicate]
I tested this using Linux 4.16-rc5. As long as I manually load all
modules in the needed order, they will all load with no symbol problems.
> All of these variables are present in the Module.symvers file in the
> /lib/modules/<kernel version>/build directory. The kernel and the
> modules versions match. I ran make clean, make, and make
> modules_install before trying to load them. I am unable to figure out
> the problem. Where I might be going wrong any ideas ?
Were you expecting some module autoloading based on their internal
dependencies? If so, maybe someone on the linux-iio mailing list
could comment on that.
--
~Randy
next prev parent reply other threads:[~2018-03-17 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 11:17 Unknown symbols in module Srishti Sharma
2018-03-17 20:42 ` Randy Dunlap [this message]
2018-03-18 11:04 ` Unknown symbols in module (iio) Jonathan Cameron
2018-03-18 12:00 ` Srishti Sharma
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=a1ceed29-158a-5ba8-6b05-cddd043baef8@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srishtishar@gmail.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®