From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next, v1] net: e1000e: solve insmod 'Unknown symbol mutex_lock' error
Date: Fri, 17 Sep 2021 09:01:42 -0700 [thread overview]
Message-ID: <20c47a57-e7d7-d791-5c86-e27310672789@intel.com> (raw)
In-Reply-To: <20210917141146.5822-1-chenhaoa@uniontech.com>
On 9/17/2021 7:11 AM, Hao Chen wrote:
> After I turn on the CONFIG_LOCK_STAT=y, insmod e1000e.ko will report:
> [ 5.641579] e1000e: Unknown symbol mutex_lock (err -2)
> [ 90.775705] e1000e: Unknown symbol mutex_lock (err -2)
> [ 132.252339] e1000e: Unknown symbol mutex_lock (err -2)
>
> This problem fixed after include <linux/mutex.h>.
Thanks for taking the time to send a patch.
Why do you think including a file will fix this? That error is usually
the user's fault for trying to use insmod which doesn't check module
dependencies.
The advice I usually give is to try modprobe instead, does the problem
still occur without this patch and just using modprobe?
prev parent reply other threads:[~2021-09-17 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 14:11 [Intel-wired-lan] [net-next, v1] net: e1000e: solve insmod 'Unknown symbol mutex_lock' error Hao Chen
2021-09-17 16:01 ` Jesse Brandeburg [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=20c47a57-e7d7-d791-5c86-e27310672789@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@osuosl.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