Chris, Here is what I verified...
>> $ uname -r 3.12.6 >> $ grep __fentry__ /proc/kallsyms Nothing found here. >> $ grep CONFIG_FTRACE /lib/modules/$(uname -r)/build/.config CONFIG_FTRACE=y CONFIG_FTRACE_SYSCALLS=y CONFIG_FTRACE_MCOUNT_RECORD=y # CONFIG_FTRACE_STARTUP_TEST is not set -----Original Message----- From: Chris Wright [mailto:chr...@redhat.com] Sent: Thursday, July 10, 2014 6:51 PM To: Daniel, Christopher Cc: Chris Wright; dev at dpdk.org Subject: Re: [dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko * Daniel, Christopher (Chris.Daniel at flukenetworks.com) wrote: > > On Jul 10, 2014, at 6:31 PM, "Chris Wright" <chrisw at redhat.com> wrote: > > * Daniel, Christopher (Chris.Daniel at flukenetworks.com) wrote: > >> 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 OK, I expected to see a suffix like 3.12.6.el...(why I assumed you built your own kernel) > >> 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?) > > 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 ? Hmm, you could verify a couple things: $ uname -r $ grep __fentry__ /proc/kallsyms $ grep CONFIG_FTRACE /lib/modules/$(uname -r)/build/.config thanks, -chris