public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Torri <storri@sbcglobal.net>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Unresolved symbols in agpart
Date: 14 Dec 2002 14:54:39 -0600	[thread overview]
Message-ID: <1039899278.17343.7.camel@base.torri.linux> (raw)
In-Reply-To: <20021214202636.GA4274@suse.de>

[-- Attachment #1: Type: text/plain, Size: 2593 bytes --]

On Sat, 2002-12-14 at 14:26, Dave Jones wrote:
> On Sat, Dec 14, 2002 at 02:08:56PM -0600, Stephen Torri wrote:
>  > I would like to help clear up the module problem in the linux kernel
>  > (2.5.51). The problem I am getting is when I do "make install" there is
>  > a report back that some symbols are unresolved. What I need to know is
>  > how these symbols are supposed to be exported? I can grep the files to
>  > find the symbols and correct this problem.
> 
> Can you try with the patch at
> ftp://ftp.kernel.org/pub/linux/kernel/people/davej/patches/2.5/2.5.51/
> 
> and let me know if that fixes things ?

It does not appear to be doing so. The version of 2.5.51 that I have is
the bitkeeper version that I grab via bk. 

Here is the output of "make install" for agpart.ko:

Kernel: arch/i386/boot/bzImage is ready
sh arch/i386/boot/install.sh 2.5.51 arch/i386/boot/bzImage System.map ""
depmod: *** Unresolved symbols in /lib/modules/2.5.51/kernel/agpgart.ko
depmod:         __alloc_pages
depmod:         remap_page_range
depmod:         preempt_schedule
depmod:         misc_deregister
depmod:         pci_find_capability
depmod:         unlock_page
depmod:         inter_module_register
depmod:         pci_bus_read_config_dword
depmod:         kmalloc
depmod:         __up_wakeup
depmod:         __get_free_pages
depmod:         vfree
depmod:         global_flush_tlb
depmod:         __page_cache_release
depmod:         no_llseek
depmod:         pm_unregister_all
depmod:         __might_sleep
depmod:         high_memory
depmod:         panic
depmod:         copy_to_user
depmod:         ioremap_nocache
depmod:         iounmap
depmod:         change_page_attr
depmod:         free_pages
depmod:         smp_call_function
depmod:         zone_table
depmod:         pm_register
depmod:         __PAGE_KERNEL
depmod:         kfree
depmod:         pci_devices
depmod:         misc_register
depmod:         vmalloc
depmod:         contig_page_data
depmod:         mem_map
depmod:         copy_from_user
depmod:         wake_up_process
depmod:         printk
depmod:         inter_module_unregister
depmod:         pci_bus_write_config_dword
depmod:         __down_failed

I grepped for "remap_page_range" found
System.map:c0149bf0 T remap_page_range
System.map:c0413a40 R __ksymtab_remap_page_range
Binary file vmlinux matches

I found that in kernel/ksym.c at line 108 is the line that is suppose to
export the symbol:

EXPORT_SYMBOL(remap_page_range);

Stephen

-- 
Stephen Torri <storri@sbcglobal.net>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2002-12-14 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14 20:08 Unresolved symbols in agpart Stephen Torri
2002-12-14 20:26 ` Dave Jones
2002-12-14 20:54   ` Stephen Torri [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=1039899278.17343.7.camel@base.torri.linux \
    --to=storri@sbcglobal.net \
    --cc=davej@codemonkey.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox