DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Habibi, Michael" <michael.f.habibi@hp.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] irq_to_desc undefined when compiling igb_uio
Date: Tue, 26 Aug 2014 20:55:29 +0000	[thread overview]
Message-ID: <845ED019F5932D4E8BED0A693FDBF6E72442E8E7@G4W3304.americas.hpqcorp.net> (raw)

All,

I am building the latest DPDK version from dpdk.org (1.7.0), last commit 8777aa. I am building with essentially the target defconfig_x86_64-native-linuxapp-gcc (renamed), using a gcc 4.4.6/eglibc 2.15 toolchain and a 2.6.34 linux kernel. During compilation, compiling the igb_uio kernel module results in the following warning:

  CC [M]  /path/to/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "irq_to_desc" [/path/to/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko] undefined!

This results in an obvious error when trying to load the module,
igb_uio: Unknown symbol irq_to_desc
insmod: cannot insert '/lib/modules/2.6.34/drivers/net/igb_uio.ko': unknown symbol in module

I have verified in our kernel source, as well as the public source for 2.6.34, that irq_to_desc is not an exported function. However the documentation states that the minimum version required is only 2.6.33. Did I setup my environment or build my kernel incorrectly?

We are building our own kernel for our use, so I have no problem rebuilding the kernel to export this symbol, but I wanted to verify with the dpdk developers first to see if this a potential bug or something I've done incorrectly. Thanks!

             reply	other threads:[~2014-08-26 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 20:55 Habibi, Michael [this message]
2014-08-26 21:32 ` Aaro Koskinen
2014-08-26 21:43   ` Habibi, Michael
2014-08-26 22:32     ` Stephen Hemminger

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=845ED019F5932D4E8BED0A693FDBF6E72442E8E7@G4W3304.americas.hpqcorp.net \
    --to=michael.f.habibi@hp.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).