DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Daniel, Christopher" <Chris.Daniel@flukenetworks.com>
To: Chris Wright <chrisw@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko
Date: Thu, 10 Jul 2014 22:44:28 +0000	[thread overview]
Message-ID: <ACC8CBEF-510A-4884-90B2-B875453487B1@flukenetworks.com> (raw)
In-Reply-To: <20140710223107.GU29905@x220.localdomain>

Actually I did not build the kernel. It is unmodified from the original centos download.
I also did not change any build parameters while building the module.
Used all the defaults from the download and executed the commands as in the quick start guide.
Is there something I can change and rebuild the dpk module ?
Thanks for your help

> On Jul 10, 2014, at 6:31 PM, "Chris Wright" <chrisw@redhat.com> wrote:
> 
> * Daniel, Christopher (Chris.Daniel@flukenetworks.com) wrote:
>> All,
>> 
>> I have the following configuration on my machine
>> 
>> Linux localhost.localdomain 3.12.6 #4 SMP Fri Dec 27 14:26:57 EST 2013 x86_64 x86_64 x86_64 GNU/Linux : Centos
>> 
>> 
>> 1)      Downloaded the latest version of DPK ( 1.7);
>> 
>> 
>> 2)      Executing the quick start instructions ( running gcc 4.7.x)
>> 
>> 
>> 
>> 3)      Having an issue with
>> 
>> 
>> 
>>      # insmod build/kmod/igb_uio.ko
>> 
>> I am getting
>> 
>> insmod: error inserting './build/kmod/igb_uio.ko': -1 Unknown symbol in module
>> 
>> dmesg:
>> igb_uio: Unknown symbol __fentry__ (err 0)
> 
> seems like you have built module w/ CONFIG_FTRACE and built kernel
> w/out.  did you manually set RTE_KERNELDIR when you built (if so, is it
> pointing to the right location?)
> 
> thanks,
> -chris

  reply	other threads:[~2014-07-10 22:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 21:53 Daniel, Christopher
2014-07-10 22:08 ` Jeff Shaw
2014-07-10 22:12   ` Daniel, Christopher
2014-07-10 22:31 ` Chris Wright
2014-07-10 22:44   ` Daniel, Christopher [this message]
2014-07-10 22:50     ` Chris Wright
2014-07-11  1:42       ` Daniel, Christopher

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=ACC8CBEF-510A-4884-90B2-B875453487B1@flukenetworks.com \
    --to=chris.daniel@flukenetworks.com \
    --cc=chrisw@redhat.com \
    --cc=dev@dpdk.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).