All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <jdeas0648@jadsystems.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: -1 Unknown symbol in module
Date: Mon, 23 Feb 2004 07:31:06 -0800	[thread overview]
Message-ID: <20040223073106.48233a67.rddunlap@osdl.org> (raw)
In-Reply-To: <200402230723.AA639631576@jadsystems.com>

On Mon, 23 Feb 2004 07:23:25 -0800 "Jim Deas" <jdeas0648@jadsystems.com> wrote:

| I am trying to recompile a 2.4.x driver to 2.6.2.
| After rebuilding the make system to use the kernel make file I was able to compile a short test module to test the system.
| I then tried my real drive and got the following error when trying to load my module
| I.E. tried
| 'insmod mymodule.ko' returned '-1 Unknown symbol in module'
| 
| I have included the module.mod.c but most important to me is where can I cross check the module symbols against the kernel to find this symbol error?

Set console loglevel to 9 ... doesn't that tell you the missing
symbol(s)?

[Use Alt+SysRq+9 or "echo 9 > /proc/sysrq-trigger".]

| Thanks,
| JD
| 
| -----------------------------------------
| #include <linux/module.h>
| #include <linux/vermagic.h>
| #include <linux/compiler.h>
|  
| MODULE_INFO(vermagic, VERMAGIC_STRING);
|  
| static const struct modversion_info ____versions[]
| __attribute_used__
| __attribute__((section("__versions"))) = {
|         { 0x12fe0ca3, "struct_module" },
|         { 0x1a1a4f09, "__request_region" },
|         { 0x7da8156e, "__kmalloc" },
|         { 0xd6ee688f, "vmalloc" },
|         { 0x41b88718, "malloc_sizes" },
|         { 0xb8cd33b5, "remove_proc_entry" },
|         { 0xeae3dfd6, "__const_udelay" },
|         { 0x1d26aa98, "sprintf" },
|         { 0xda02d67, "jiffies" },
|         { 0xd533bec7, "__might_sleep" },
|         { 0xc280a525, "__copy_from_user_ll" },
|         { 0x865ebccd, "ioport_resource" },
|         { 0x1b7d4074, "printk" },
|         { 0xcfaa1ea9, "pci_find_device" },
|         { 0xed5c73bf, "__tasklet_schedule" },
|         { 0xcbf92b8b, "__down_failed_trylock" },
|         { 0x28c3bbf5, "__down_failed_interruptible" },
|         { 0xf1d0cdab, "__check_region" },
|         { 0x306c0d42, "kmem_cache_alloc" },
|         { 0xab600421, "probe_irq_off" },
|         { 0x3762cb6e, "ioremap_nocache" },
|         { 0x6050990a, "schedule_delayed_work" },
|         { 0x26e96637, "request_irq" },
|         { 0x4292364c, "schedule" },
|         { 0x32dd738e, "register_chrdev" },
|         { 0x9c72f3ff, "create_proc_entry" },
|         { 0xd49501d4, "__release_region" },
|         { 0xbfeef0a1, "__wake_up" },
|         { 0xb121390a, "probe_irq_on" },
|         { 0x37a0cba, "kfree" },
|         { 0x5fb196d4, "iounmap" },
|         { 0xc192d491, "unregister_chrdev" },
|         { 0xd22b546, "__up_wakeup" },
|         { 0xaac07a8f, "pci_enable_device" },
|         { 0xf20dabd8, "free_irq" },
| };
|  
| static const char __module_depends[]
| __attribute_used__
| __attribute__((section(".modinfo"))) =
| "depends=";


--
~Randy

      reply	other threads:[~2004-02-23 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 15:23 -1 Unknown symbol in module Jim Deas
2004-02-23 15:31 ` Randy.Dunlap [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=20040223073106.48233a67.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=jdeas0648@jadsystems.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.